Linked API

nv_fetch_person

Read-only

Allows you to open a person page in Sales Navigator to retrieve their basic information (nv.openPersonPage action). The result carries urn — the person's permanent LinkedIn member URN (urn:li:member:) — and companyUrn for their current company (urn:li:organization:); either is null when LinkedIn does not expose it. The same person carries the same urn in standard interface results, so it can be used to match Sales Navigator results against them.

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": {
      "personHashedUrl": "<personHashedUrl>"
    },
    "name": "nv_fetch_person"
  }
}

Input Schema

Name	Required	Description	Default
`personHashedUrl`	Yes	Public or hashed LinkedIn person URL (/in/... or /sales/lead/...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / personHashedUrl / description

Previous value: -"Hashed LinkedIn URL of the person."New value: +"Public or hashed LinkedIn person URL (/in/... or /sales/lead/...)."

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description discloses the key behavioral trait — the action is queued into a cloud-browser workflow, returns immediately with a status snapshot, may take several minutes, and can be parked outside working hours. It also documents the returned urn/companyUrn fields and their null semantics, which annotations cannot convey.

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?

It is long, but front-loaded with purpose and result shape before the async workflow mechanics, and each paragraph (return fields, polling handoff, pendingReason semantics) carries distinct operational value. Slightly verbose in places, but no sentence is wasted.

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 a single-parameter async tool with no output schema, the description covers everything an agent needs: what it does, what the immediate response looks like, how to get the final result, and how to interpret non-terminal states. Nothing material is left to inference.

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 coverage is 100% and the single personHashedUrl parameter is already documented as accepting public or hashed LinkedIn person URLs (/in/... or /sales/lead/...). The description adds no further constraints or formatting detail about this parameter, so the baseline 3 applies.

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

Purpose5/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 in Sales Navigator to retrieve their basic information' — and names the underlying action (nv.openPersonPage). It also distinguishes the result from standard-interface data by explaining that the returned urn lets Sales Navigator results be matched against them, which separates it from the sibling fetch_person tool.

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

Usage Guidelines5/5

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

Gives explicit routing instructions: after the call returns a pending/running snapshot, use get_workflow_result with the returned workflowId and operationName, and explicitly says not to retry the original tool while a workflow is still running. It also tells the agent what to do for the 'outsideWorkingHours' pendingReason (report to the user rather than loop).

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.