Linked API

nv_search_people

Read-only

Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action). Either term or customSearchUrl must be provided. Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member:), or 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. Every person also carries viewerState.connectionDegree — your connection degree to them (1st, 2nd, 3rd+), or null when LinkedIn shows none.

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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nv_search_people"
  }
}

Input Schema

Name	Required	Description
`term`	No	Optional. Keyword or phrase to search. Required unless customSearchUrl is specified.
`limit`	No	Optional. Number of search results to return. Defaults to 25, with a maximum value of 2500.
`filter`	No	Optional. Object that specifies filtering criteria for people. When multiple filter fields are specified, they are combined using AND logic.
`customSearchUrl`	No	Optional. URL copied from a Sales Navigator people search page (linkedin.com/sales/search/people/...). When specified, overrides term and filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedInput schema / properties / customSearchUrl

Added value: +{
+  "description": "Optional. URL copied from a Sales Navigator people search page (linkedin.com/sales/search/people/...). When specified, overrides term and filter.",
+  "type": "string"
+}

changedInput schema / properties / term / description

Previous value: -"Optional. Keyword or phrase to search."New value: +"Optional. Keyword or phrase to search. Required unless customSearchUrl is specified."

First observedOct 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses critical async workflow behavior: queued cloud-browser execution, immediate pending/running responses, workflowId and operationName retrieval via get_workflow_result, no-retry guidance, and the meaning of pendingReason values including working-hours parking. It also documents returned urn and connectionDegree fields, including nullability, which is especially valuable because there is no output schema.

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

Conciseness5/5

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

The purpose is front-loaded, and the remaining paragraphs are organized around the two non-obvious concerns an agent must understand: async workflow retrieval and pendingReason handling. Despite its length, the detail is warranted by the workflow complexity and no sentences are 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 complex async search tool with no output schema, the description covers the necessary operational facts: how to invoke it, what happens immediately, how to retrieve results, how to avoid duplicate work, and what some returned fields mean. It is sufficiently complete for an agent to call and follow up correctly.

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 the schema already documents term, limit, nested filters, and customSearchUrl override behavior. The description reinforces the term/customSearchUrl requirement but does not add much parameter-level meaning beyond what the schema already provides.

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?

The description states a specific verb and resource: searching people in Sales Navigator with filtering criteria. It implicitly distinguishes Sales Navigator results from standard LinkedIn results by discussing matching URNs against standard interface results, but it does not explicitly name the sibling search_people tool as the alternative.

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?

It clearly establishes the Sales Navigator people-search context and states that either term or customSearchUrl must be provided. It also explains that customSearchUrl overrides term and filter, though it does not explicitly say when to choose this tool over search_people or 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.