Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Resolve LinkedIn person

linkedin_live_person_resolve_v2
Read-onlyIdempotent

Resolve a LinkedIn profile handle or /in/ URL to a person entity ID for identity matching and profile enrichment.

Instructions

Resolve a LinkedIn handle to a person entity id. Requires handle.

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

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. LinkedIn profile handle. Not an organization slug. A /in/{handle} 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that: it does not say what an entity id looks like, whether the resolution is cached or rate-limited, or what happens when the handle is invalid or ambiguous.

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 purpose. The second sentence largely repeats the schema's required-field marking, so it is close to waste but harmless at this length.

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?

The tool is simple, annotations are rich, and there is no output schema, so the description need not explain return values. However, because there is no output schema, some hint about what the returned entity id is used for would close the remaining gap; as written, the definition is only just sufficient.

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 all four parameters are documented in the schema itself, including the handle format ('/in/{handle} URL is accepted'). The description only restates the requirement for handle and adds no format or semantic detail beyond the schema; 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 (resolve) and a specific transformation (LinkedIn handle → person entity id), which is unambiguous on its own. It does not explicitly contrast with the sibling linkedin_live_organization_resolve_v2 or linkedin_live_profile_get_v2, so the sibling distinction is left to the schema's 'Not an organization slug' note.

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 rather than people_search or profile_get, nor any stated precondition such as 'use this first to obtain an id for the person_* tools'. 'Requires handle' is an input constraint, not 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