Linked API

fetch_person

Read-only

Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions. The basic information carries urn — the person's permanent LinkedIn member URN (urn:li:member:), or null when LinkedIn does not expose it. Retrieved posts carry urn on their author and reposter as well. ⚠️ PERFORMANCE WARNING: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time: 💡 Recommendation: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

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": {
      "personUrl": "<personUrl>"
    },
    "name": "fetch_person"
  }
}

Input Schema

Name	Required	Description
`personUrl`	Yes	The LinkedIn profile URL of the person to fetch (e.g., 'https://www.linkedin.com/in/john-doe')
`retrievePosts`	No	Optional. Whether to retrieve the person's posts information. Default is false.
`retrieveSkills`	No	Optional. Whether to retrieve the person's skills information. Default is false.
`retrieveComments`	No	Optional. Whether to retrieve the person's comments information. Default is false.
`retrieveEducation`	No	Optional. Whether to retrieve the person's education information. Default is false.
`retrieveLanguages`	No	Optional. Whether to retrieve the person's languages information. Default is false.
`retrieveReactions`	No	Optional. Whether to retrieve the person's reactions information. Default is false.
`retrieveExperience`	No	Optional. Whether to retrieve the person's experience information. Default is false.
`postsRetrievalConfig`	No	Optional. Configuration for retrieving posts. Available only if retrievePosts is true.
`commentsRetrievalConfig`	No	Optional. Configuration for retrieving comments. Available only if retrieveComments is true.
`reactionsRetrievalConfig`	No	Optional. Configuration for retrieving reactions. Available only if retrieveReactions is true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by explaining that actions are queued into a cloud-browser workflow, that the server returns a pending snapshot shape, and by decoding `pendingReason` values ('queued' vs 'outsideWorkingHours') including the fact that outside-working-hours returns immediately rather than polling. It also warns that each extra retrieval flag significantly increases execution time and documents the URN field semantics including its null case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the performance warning are front-loaded, which is good, but the middle section ends with a dangling colon ('Each additional parameter significantly increases execution time:') followed by no list, then jumps to the recommendation — a structural defect. The workflow-mechanics paragraph is dense but does earn its place for an async tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with nested config objects, no output schema, and an asynchronous execution model, the description supplies the missing contract: the immediate return shape, how to long-poll for the result, and the two non-terminal pending states. Nothing an agent needs in order to call this and follow up correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning on top by framing the boolean flags as a cost tradeoff rather than neutral options and by explaining that retrieved posts carry `urn` on author and reposter. It does not explain the interaction requirements beyond what the schema's nested `*RetrievalConfig` descriptions already state ('available only if retrievePosts is true').

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 ('open a person page to retrieve their basic information') and enumerates the optional data categories (experience, education, skills, languages, posts, comments, reactions). It is clear what the tool does, but it never distinguishes itself from the sibling `nv_fetch_person`, which an agent would reasonably confuse with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage guidance: start with basic info only, enable extra flags only when the user explicitly asks, and do not retry the tool while a workflow is running — instead call `get_workflow_result` with the returned workflowId/operationName. That names an alternative tool and the condition that selects it. The missing piece is any guidance on when to prefer this over `nv_fetch_person`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Linked API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.