Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn recommendations

linkedin_live_person_recommendations_v2
Read-onlyIdempotent

Retrieve LinkedIn person recommendations using a required entity ID to help identify relevant people for networking, research, or outreach.

Instructions

Get recommendations for a LinkedIn person. Requires entityId. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
entityIdYesRequired. LinkedIn person entity ID. 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 structured. The description adds only 'Returns a list' — no indication of what the recommendations contain, how many, whether pagination applies, or any per-call constraints.

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 short sentences, front-loaded with the action and resource, with no filler. The middle sentence largely duplicates the schema's required-parameter declaration, which is minor redundancy but not bloat.

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, read-only, idempotent lookup with rich annotations, the definition covers the core contract. However, with no output schema present, the description should say more about the shape or scope of the returned recommendations than 'Returns a list.'

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%, including the note that entityId is a person entity ID and not a vanity handle, so the schema carries parameter meaning. The description's 'Requires entityId' merely restates what the required array already provides, so baseline 3 is appropriate.

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 recommendations for a LinkedIn person.' That is enough to separate it from siblings like posts, comments, or interests, though it does not explicitly contrast with the nearest neighbor (linkedin_live_person_similar_v2).

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?

The only guidance is a prerequisite ('Requires entityId'), which is already expressed by the required-parameter list in the schema. There is no statement of when to choose this over similar_v2, interests_v2, or profile_get, and no exclusions.

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