Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn grouped employment history

linkedin_live_person_employmentHistory_v2
Read-onlyIdempotent

Retrieves grouped employment history for a LinkedIn person using the required entity ID, returning a structured list of roles and organizations.

Instructions

Get grouped employment history 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_employmentHistory_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds only "Returns a list," which is thin but slightly useful given there is no output schema; it says nothing about pagination, result size, or behavior when a person has no history.

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, front-loaded sentences with no filler; the resource and prerequisite come first. The brevity is efficient but edges toward under-specification for a tool whose behavior is not otherwise documented.

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 read-only list tool with full schema coverage and strong annotations, the essentials are present, but the missing explanation of "grouped" output shape and the absent pointer to the resolve tool leave real workflow gaps. With no output schema, one more sentence about what the list contains would materially help.

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 entityId, context, llm_model, and conversation_id are all documented in the schema itself, establishing a baseline of 3. The description repeats the entityId requirement and adds no new meaning, such as what a valid ID looks like beyond "not a vanity handle" or when conversation_id must be supplied.

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 grouped employment history for a LinkedIn person." An agent knows exactly what data comes back, but nothing distinguishes it from related person tools such as profile_get_v2 or recommendations_v2, and "grouped" is never explained.

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 "Requires `entityId`," which is a prerequisite rather than a when-to-use rule. It never says when to prefer this over linkedin_live_profile_get_v2, nor does it point at linkedin_live_person_resolve_v2 for obtaining an entityId from other identifiers.

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