Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn company page

linkedin_company_get
Read-onlyIdempotent

Retrieve a LinkedIn company page by URL or vanity slug to get organization details for research, lead enrichment, or company verification.

Instructions

Get a LinkedIn company page by company URL — use linkedin_live_organization_resolve_v2 then linkedin_live_organization_get_v2 for schools and mixed organization pages. Requires url. url takes the vanity slug (linkedin.com/company/google, or just "google"). For a numeric company id, use linkedin_live_organization_get_v2 with 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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_company_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. LinkedIn company page URL for this lookup. School and organization-guest pages are not supported; use `GET /v2/linkedin/organizations/resolve` or `GET /v2/linkedin/organizations`.
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

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real scoping behavior — which page types are unsupported and that callers must hop to another tool for them — but says nothing about return shape, caching, or failure modes for invalid slugs.

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 tight sentences, front-loaded with the action and the disambiguation rule before the parameter detail. Minor waste: 'Requires `url`' restates a field the schema already marks required.

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

Completeness4/5

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

For a simple read tool with full annotation coverage and full schema coverage, the description supplies everything needed to route and call it correctly. The only gap is that it never hints at what the returned company page contains, though this is a low-complexity lookup where that is a minor omission.

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

Parameters4/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 earns a bump by clarifying the `url` parameter accepts either a full `linkedin.com/company/google` URL or a bare vanity slug, and by ruling out numeric ids in that slot. The other three parameters (context, llm_model, conversation_id) are left entirely to their schema text, which is acceptable.

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

Purpose5/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 company page by company URL') and immediately disambiguates against the closest siblings: schools/mixed orgs go through `linkedin_live_organization_resolve_v2` + `linkedin_live_organization_get_v2`, numeric ids go straight to `linkedin_live_organization_get_v2`. An agent can pick between these tools without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules with named alternatives and the conditions that select them (school/org-guest pages, numeric company id). It effectively defines when this tool is the wrong choice, which is exactly what a sibling-heavy namespace needs.

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