Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List affiliated LinkedIn organizations

linkedin_live_organization_affiliated_v2
Read-onlyIdempotent

Retrieves affiliated organizations for a specified LinkedIn organization ID, returning a list you can use to map corporate relationships and verify page associations.

Instructions

List affiliated organizations 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_affiliated_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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only "Returns a list", which is thin and says nothing about pagination, result size, affiliation semantics, or rate limits — nothing beyond what the annotations already convey.

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, front-loaded sentences with no filler. "Returns a list" is slightly redundant but does orient the reader before they open the schema.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and complete annotations, the definition is minimally adequate. With no output schema, though, it should say what an affiliated organization record contains and whether results are paginated — "Returns a list" is too vague to close that gap.

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%, with each of the four parameters documented in the schema itself. The description merely repeats that organizationId is required and adds no meaning about its format (the numeric pattern) or about context, llm_model, and conversation_id, so the baseline of 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?

The description uses a specific verb and resource ("List affiliated organizations for a LinkedIn organization"), which is clearer than a bare restatement of the title. It does not, however, distinguish this from closely named siblings such as linkedin_live_organization_get_v2 or linkedin_live_organization_similar_v2, leaving the agent to infer what an 'affiliation' is versus a similar org.

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?

The only guidance is the prerequisite "Requires `organizationId`", which is already enforced by the required field in the schema. There is no statement of when to pick this over organization_get_v2, organization_similar_v2, or organizations_search_v2, and no exclusions.

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