Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn organization

linkedin_live_organization_get_v2
Read-onlyIdempotent

Retrieve a LinkedIn organization's profile by slug or numeric ID. Use this to look up company or school details from a LinkedIn URL.

Instructions

Get a LinkedIn organization by slug or id. Optional inputs: slug and id.

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

Input Schema

NameRequiredDescriptionDefault
idNoNumeric LinkedIn organization ID.
slugNoLinkedIn organization slug. A /company/{slug} or /school/{slug} URL is accepted.
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

B3.1/5.0
Behavior3/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 nothing beyond that except the lookup keys, which the schema already contains. It omits whether a missing organization errors or returns null, and what happens if both keys are supplied and conflict.

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, front-loaded sentences with no padding. The second sentence largely restates parameter names the schema already defines, so it is efficient but not maximally informative.

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?

No output schema exists, so the description should convey what an organization record contains or how it differs from the batch, affiliated, headcount, and resolve siblings. It conveys none of that, and for a 5-parameter tool with analytics context requirements it is under-specified.

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 coverage is 100%, so the baseline is 3. The description does not add the one semantic constraint the schema lacks: that at least one of slug or id must be provided for identification. Calling both "optional" without that caveat may mislead an agent into omitting both.

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 a LinkedIn organization" — plus the two lookup keys (slug or id). It is clear what the tool returns conceptually, but it does not distinguish itself from near neighbors such as linkedin_live_organization_resolve_v2 or linkedin_company_get.

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?

No guidance on when to use this versus resolve_v2, organizations_search_v2, or company_get. It also does not say which lookup key to prefer when both slug and id are available, leaving the agent to guess.

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