Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn organizations

linkedin_live_organization_batch_v2
Read-onlyIdempotent

Fetch LinkedIn organization and school page data from up to 50 URLs in one request to gather company info for research or enrichment.

Instructions

Get LinkedIn organizations by URL. Requires url.

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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_organization_batch_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired.
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.
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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of partial-batch failure behavior, rate limits, cost, or what happens when some URLs in the array are invalid.

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?

Two short sentences, front-loaded with the action and immediately followed by the required input. Nothing is wasted, though the brevity reflects under-specification rather than disciplined editing.

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 batch tool accepting 1-50 URLs with no output schema, the description should explain batching semantics, expected results ordering, and failure handling for invalid URLs. None of that is present, leaving key operational questions unanswered despite the rich annotations.

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, including the URL path constraints and the context/llm_model/conversation_id fields, are already documented in the schema. The description only restates that `url` is required, adding no meaning beyond what the schema provides; baseline 3 applies.

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

Purpose3/5

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

The description names a verb and resource ("Get LinkedIn organizations") plus an input mechanism ("by URL"), which is specific enough to understand the basic action. However, it never conveys the defining batch behavior implied by the tool name (up to 50 URLs), and does not distinguish it from the sibling linkedin_live_organization_get_v2, which appears to do a single-organization lookup.

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 batch tool versus the singular get variant, the search tool, or the resolve tool. The only conditional statement is "Requires `url`," which is a requirement rather than usage guidance.

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