Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Resolve LinkedIn organization

linkedin_live_organization_resolve_v2
Read-onlyIdempotent

Resolve a LinkedIn organization slug to its organization ID so you can target the correct company in LinkedIn workflows.

Instructions

Resolve a LinkedIn organization slug to an organization id. Requires slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYesLinkedIn organization slug. Not a person handle.
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

A3.5/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 by structured data. The description adds nothing beyond that — it does not mention the conversation_id handshake that constrains call ordering, nor any rate limits or output characteristics. Given rich annotations, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the purpose front-loaded and zero filler. The only mild redundancy is 'Requires `slug`', which restates the schema's required list, but it is a single clause and does not bloat the definition.

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 resolver with full annotation coverage and no output schema, the description covers the core contract. However, it omits the multi-step conversation_id chaining behavior that governs how the tool must be invoked, which is the main complexity an agent faces here.

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% and every parameter, including context, llm_model and conversation_id, is documented in the schema with more detail than the description. The description mentions only `slug`, which the schema already marks required, so it adds no meaning beyond the structured fields. Baseline 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?

States a specific verb and resource: 'Resolve a LinkedIn organization slug to an organization id', which is precise enough to separate it from linkedin_live_person_resolve_v2 and from search tools. It never names the sibling it pairs with (organization_get_v2) or the search alternative, so sibling differentiation relies on the tool name rather than the prose.

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

Usage Guidelines3/5

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

Usage is only implied: you call this when you hold a slug and need an id. There is no explicit when-to-use or when-not-to-use guidance, no mention of using linkedin_live_organizations_search_v2 to obtain a slug first, and no note that organization_get_v2 is the right tool once an id is known.

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