Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List similar LinkedIn organizations

linkedin_live_organization_similar_v2
Read-onlyIdempotent

Find similar LinkedIn organizations by numeric organization ID to identify comparable companies for research, prospecting, or market mapping. Returns a list.

Instructions

List similar LinkedIn organizations. 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_similar_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 covered. The description adds essentially nothing beyond them: "Returns a list" is the bare shape, with no mention of result count, pagination, ordering, or what happens when an org has no similar peers. The two-sentence text is mostly a restatement of the required parameter.

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 very short sentences, front-loaded with purpose and with no filler or hedging. It is efficient, though its brevity is closer to under-specification than to disciplined economy.

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?

There is no output schema, so the description must characterize the return value, yet it offers only "Returns a list" with no indication of item fields, size, or ordering. For an open-world read tool with four parameters, that leaves the agent guessing about the shape of the result.

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%, including detailed guidance on context, llm_model and conversation_id, so the schema carries the parameter burden and a baseline 3 applies. The description's only parameter remark ("Requires `organizationId`") merely repeats the required array and adds no semantic depth about the ID format or its effect on results.

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 names a specific verb and resource ("List similar LinkedIn organizations"), which separates it from get/affiliated/search siblings by name alone. It is clear what the tool returns conceptually (similar orgs), though it never defines what "similar" means or how similarity is derived.

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 "Requires `organizationId`", which is a prerequisite rather than when-to-use advice. There is no statement of when to reach for this versus linkedin_live_organization_affiliated_v2 or linkedin_live_organizations_search_v2, and no exclusion criteria.

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