All skills
linkedin Brand & Social Listening

Employee Advocacy vs Official Voice

Measure whether your employees — and the wider public — out-amplify your own company page on LinkedIn

Run this skill with your agent
1. Connect the MCP server
https://apidirect.io/mcp?token=YOUR_API_KEY
2. Then ask your agent — name the skill so it runs this exact playbook
Use the employee-advocacy-vs-official-voice skill: Tell me whether {company} employees amplify the brand more than its official LinkedIn page
Naming the skill (employee-advocacy-vs-official-voice) makes your agent run this exact playbook instead of improvising its own searches. In clients that support MCP prompts (Claude Desktop, Claude Code, Cursor) it also appears as a prompt named employee-advocacy-vs-official-voice, and any agent can call get_skill(skill_id="employee-advocacy-vs-official-voice") directly.

What it does

LinkedIn uniquely splits posts BY the company page (from_company) from posts BY its employees (author_company) and posts that merely mention it (mentions_company); comparing these three voices by volume, sentiment, and engagement reveals whether your real brand reach is the page, your people, or the wider market. Optional topic, seniority (author_title), and sort controls let you focus the read on a campaign or a specific rank of employee.

Who it's for: Employer brand, internal comms, and social leads benchmarking advocacy

Inputs

Input Required Description Example
company Yes Company name to analyze HubSpot
topic No Optional. Narrow every voice (page, employees, mentions) to posts about a specific campaign, product, or theme. Maps to the search_linkedin query param. Omit to read all posts. AI product launch
focus_title No Optional. Restrict the employee-voice capture to a specific role or seniority to see which ranks actually amplify. Maps to the search_linkedin author_title param. Omit to include all employees. VP
sort_by No Optional. How to rank captured posts. Maps to the search_linkedin sort_by enum (most_recent or relevance). Defaults to most_recent. most_recent

How your agent runs it

  1. 1
    search_linkedin_companies(query={company})

    Resolve the brand to its numeric company_id and LinkedIn company url.

  2. 2
    search_linkedin(from_company=<company_id>, query={topic}, sort_by=most_recent, get_sentiment=true)

    Capture the official brand-page posts as the engagement and sentiment baseline. {topic} and {sort_by} are optional — omit {topic} to read all posts; sort_by defaults to most_recent.

  3. 3
    search_linkedin(author_company=<company_id>, author_title={focus_title}, query={topic}, sort_by=most_recent, get_sentiment=true)

    Capture posts written by employees of that company and their sentiment, noting the most influential voices. Optional {focus_title} narrows to a seniority or role (e.g. VP, Engineer) to see which ranks amplify; omit it to include all employees.

  4. 4
    search_linkedin(mentions_company=<company_id>, query={topic}, sort_by=most_recent, get_sentiment=true)

    Capture the wider 'earned voice' — posts that mention the brand from people who are neither the page nor its employees; net out the page and employee posts to isolate genuine third-party advocacy.

  5. 5
    linkedin_company_details(url=<company_url>)

    Pull employee count to normalize employee-post volume, then compute the advocacy amplification ratio of employee reach versus official reach (and versus earned third-party reach).

Delivers: An advocacy report comparing three voices — official brand-page posts, employee posts, and earned third-party mentions — by volume, sentiment, and engagement, normalized by headcount into an amplification ratio, with your top employee voices and an optional breakdown by seniority or campaign topic.

Tools used

The full playbook

This is exactly what the MCP returns to your agent (via the employee-advocacy-vs-official-voice prompt or get_skill tool), with your inputs filled in.

SKILL: Employee Advocacy vs Official Voice
LinkedIn uniquely splits posts BY the company page (from_company) from posts BY its employees (author_company) and posts that merely mention it (mentions_company); comparing these three voices by volume, sentiment, and engagement reveals whether your real brand reach is the page, your people, or the wider market. Optional topic, seniority (author_title), and sort controls let you focus the read on a campaign or a specific rank of employee.

You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.

INPUTS:
  - company (required): <company — ASK THE USER>
      Company name to analyze
  - topic (optional): (optional — e.g. AI product launch)
      Optional. Narrow every voice (page, employees, mentions) to posts about a specific campaign, product, or theme. Maps to the search_linkedin query param. Omit to read all posts.
  - focus_title (optional): (optional — e.g. VP)
      Optional. Restrict the employee-voice capture to a specific role or seniority to see which ranks actually amplify. Maps to the search_linkedin author_title param. Omit to include all employees.
  - sort_by (optional): most_recent (default — override if you like)
      Optional. How to rank captured posts. Maps to the search_linkedin sort_by enum (most_recent or relevance). Defaults to most_recent.

STEPS:
  1. Tool `search_linkedin_companies` — search_linkedin_companies(query={company})
     Resolve the brand to its numeric company_id and LinkedIn company url.
  2. Tool `search_linkedin` — search_linkedin(from_company=<company_id>, query={topic}, sort_by=most_recent, get_sentiment=true)
     Capture the official brand-page posts as the engagement and sentiment baseline. {topic} and most_recent are optional — omit {topic} to read all posts; sort_by defaults to most_recent.
  3. Tool `search_linkedin` — search_linkedin(author_company=<company_id>, author_title={focus_title}, query={topic}, sort_by=most_recent, get_sentiment=true)
     Capture posts written by employees of that company and their sentiment, noting the most influential voices. Optional {focus_title} narrows to a seniority or role (e.g. VP, Engineer) to see which ranks amplify; omit it to include all employees.
  4. Tool `search_linkedin` — search_linkedin(mentions_company=<company_id>, query={topic}, sort_by=most_recent, get_sentiment=true)
     Capture the wider 'earned voice' — posts that mention the brand from people who are neither the page nor its employees; net out the page and employee posts to isolate genuine third-party advocacy.
  5. Tool `linkedin_company_details` — linkedin_company_details(url=<company_url>)
     Pull employee count to normalize employee-post volume, then compute the advocacy amplification ratio of employee reach versus official reach (and versus earned third-party reach).

DELIVER: An advocacy report comparing three voices — official brand-page posts, employee posts, and earned third-party mentions — by volume, sentiment, and engagement, normalized by headcount into an amplification ratio, with your top employee voices and an optional breakdown by seniority or campaign topic.

Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.