Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn interests

linkedin_live_person_interests_v2
Read-onlyIdempotent

Retrieve a LinkedIn person's interests using their entity ID to understand professional topics and engagement areas; returns a structured list for profile enrichment.

Instructions

Get interests 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_interests_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.7/5.0
Behavior2/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 only 'Returns a list', which is near-zero behavioral insight — nothing about live-fetch latency, rate limits, partial results, or what happens with an invalid/stale entityId, despite openWorldHint implying external variability.

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, action front-loaded, no filler prose. It loses a point because 'Requires entityId' and 'Returns a list' duplicate structured information instead of carrying new meaning.

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 single-entity read with full schema coverage, full annotation coverage, and no output schema, the description is close to sufficient — no return-value documentation is expected. What is missing is a definition of 'interests' and any hint that the entityId must be a resolved entity ID, leaving the agent to infer the payload from the tool name.

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% and every parameter carries its own constraint text, so the schema does the heavy lifting. The description repeats that entityId is required without adding format, provenance, or failure semantics beyond it — baseline 3 applies.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource pair ('Get interests for a LinkedIn person'), which is better than a bare name restatement, but 'interests' is never defined — it could mean skills, follows, endorsements, or group memberships. The sibling names differentiate by resource noun alone, so the agent still cannot tell exactly what data this returns.

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, no mention of needing to resolve a person first (sibling linkedin_live_person_resolve_v2 exists), and no exclusions. The only directional content is 'Requires entityId', which is already in the schema's required list.

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