Linked API

nv_retrieve_list_accounts

Read-only

Retrieve list accounts from an owned Sales Navigator list. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveListAccounts.

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": {
      "listId": "<listId>"
    },
    "name": "nv_retrieve_list_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum matching members, 1–1000; default 25.
`listId`	Yes	Owned list ID as a string, never a number.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true, which is a thin safety profile. The description goes far beyond: it discloses that the call is queued into a cloud-browser workflow, returns immediately with a status snapshot, may take several minutes, can be parked by account working hours, and that retrying spawns duplicate queued work. That is exactly the behavioral context 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.

Conciseness3/5

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

Purpose is front-loaded and the workflow protocol follows logically, but the prose is roughly 200 words with redundancy: the long-poll behavior and the 'return another in-progress snapshot' idea are restated across sentences. The 'Plus required' fragment and the duplicated polling explanation cost it.

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

Completeness4/5

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

For a 2-parameter, no-output-schema tool, the description covers the return shape of the acknowledgement (status, pendingReason, workflowId, operationName, message) and the retrieval path. It does not describe the shape of the final list-accounts payload an agent will eventually receive, which is the one remaining gap.

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 both limit (1-1000, default 25) and listId ('as a string, never a number') are already documented in the schema. The description adds no syntax, format, or edge-case meaning beyond that, so the baseline 3 applies.

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: 'Retrieve list accounts from an owned Sales Navigator list.' An agent can tell it apart from siblings such as nv_retrieve_list_leads and nv_retrieve_lists by the resource noun, though the description never explicitly contrasts them. The stray fragment 'Plus required' is noise that slightly muddies the opening.

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 explicit operational guidance: call get_workflow_result with the returned workflowId and operationName, and 'Do not retry the original tool while a workflow is still running; that creates duplicate queued work.' The pendingReason branches (queued vs outsideWorkingHours) tell the agent what to do in each case. It stops short of saying when to choose this over nv_retrieve_list_leads, so it is not a full 5.

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.