Linked API

nv_retrieve_lists

Read-only

Plus-only root action nv.retrieveLists. Retrieve every owned Sales Navigator list of the requested type. Results contain id (string), name, type (lead/account), source (open upstream string), entityCount (number or null), and url. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveLists. Final data is the list array.

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": {
      "type": "<type>"
    },
    "name": "nv_retrieve_lists"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes	Owned list type to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that execution is queued into a cloud-browser workflow, may take several minutes, returns an immediate {status, pendingReason, workflowId, operationName, message} snapshot, and what each pendingReason means including parking until the next working day. That is exactly the kind of behavior annotations cannot express.

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 result shape are front-loaded, which is good, but the following two paragraphs are largely generic workflow boilerplate that could be compressed. The pendingReason discussion is useful but verbose relative to a one-parameter read 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?

There is no output schema, yet the description enumerates the returned list fields (id, name, type, source, entityCount, url) and where the final data lives (the list array after workflow completion). Combined with the async retrieval instructions, an agent has everything needed to call it and follow up.

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% with a single enum parameter, so the schema already carries the parameter meaning. The description only restates the lead/account distinction when enumerating result fields; it adds no new detail such as whether an empty list type is valid or what 'owned' excludes.

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 every owned Sales Navigator list of the requested type') and names the upstream action (nv.retrieveLists) plus the type/lead-account split. It does not explicitly distinguish itself from close siblings like nv_retrieve_list_leads or nv_retrieve_list_accounts, which return list contents rather than the lists themselves, so the agent must infer that boundary.

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?

Strong operational guidance: it tells the agent to call get_workflow_result with the returned workflowId/operationName, and explicitly warns 'Do not retry the original tool while a workflow is still running'. It also explains how to react to 'queued' vs 'outsideWorkingHours' pending states. What is missing is guidance on when to choose this tool over sibling list/search tools (e.g., nv_retrieve_saved_searches or the per-list retrieval tools).

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.