Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn profile

linkedin_live_profile_get_v2
Read-onlyIdempotent

Retrieve a LinkedIn profile by handle or entity ID to access person details for social data lookups and profile research.

Instructions

Get a LinkedIn profile by handle or entity id. Optional inputs: handle and entityId.

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_profile_get_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoLinkedIn 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.
entityIdNoLinkedIn person entity ID. Opaque; often ACo…. Not a vanity handle.
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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no note on what a miss returns, whether both identifiers may be combined, or what the profile payload contains — so it does little work the annotations have not already done.

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 with the core action front-loaded and no filler. The second sentence largely repeats what the schema already shows, which is mild waste but not enough to hurt readability.

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?

This is a simple single-resource lookup with no output schema and a fully documented input schema, so the description needn't explain return values. Still, for a tool that accepts two mutually alternative identifiers, it should state precedence or mutual exclusivity and what happens on a miss; that gap keeps it at minimum viable.

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 handle, entityId, context, llm_model and conversation_id are all documented in the schema itself, which sets the baseline at 3. The description merely restates that handle and entityId are optional inputs rather than adding resolution rules, so it neither helps nor harms beyond the schema.

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?

The description names a specific verb and resource ("Get a LinkedIn profile") and adds that the lookup key can be a handle or entity id, which is clearer than the name alone. It does not, however, distinguish this from nearby siblings such as linkedin_live_person_resolve_v2 or linkedin_live_profile_batch_v2, so the agent gets no help choosing among them.

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 when-to-use guidance at all: no statement of when a single profile fetch is preferable to person_resolve_v2 or the batch variant, and no note on prerequisites or failure conditions. The phrase "Optional inputs" only hints that the two identifiers are alternatives, without saying which wins or what happens if neither is supplied.

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