Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn organization headcount

linkedin_live_organization_headcount_v2
Read-onlyIdempotent

Fetches headcount for a LinkedIn organization by numeric organization ID, returning a list for workforce size analysis.

Instructions

Get headcount for a LinkedIn organization. Requires organizationId. Returns a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_organization_headcount_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
organizationIdYesNumeric LinkedIn organization ID.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's one genuine addition is 'Returns a list', which tells the agent the payload is array-shaped rather than a scalar total — useful since there is no output schema — but it says nothing about what each element contains, pagination, or freshness of the headcount data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no redundancy, and the core action is front-loaded before the requirement and return notes. It is close to minimal, though the sentence fragments read more like notes than a coherent instruction set.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool this is thin: it never explains the three protocol parameters it mandates (context, llm_model, conversation_id), nor how to source organizationId from the resolve sibling, nor what the returned list elements represent. The absence of an output schema means the description should carry more of the return-value burden than a vague 'Returns a list'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (organizationId, context, llm_model, conversation_id) are already documented, including the numeric pattern and the conversation_id echo rule. The description only restates that organizationId is required, adding no format or sourcing detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get headcount for a LinkedIn organization'), which cleanly separates it from siblings like organization_posts_v2 or organization_jobs_v2 that return other data about the same entity. It does not name any sibling explicitly, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives such as linkedin_live_organization_get_v2 (which likely returns the same org's profile fields) or organization_similar_v2. 'Requires `organizationId`' states a prerequisite but not an occasion for use, and nothing says where an agent should obtain that ID (e.g., from organization_resolve_v2).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools