Linked API

nv_save_lead

Plus-only root action nv.saveLead. Ensure a lead is saved; with listId, also ensure membership in that one list, leaving other lists untouched. Without listId, leave lists unchanged. Repeating succeeds without changes. Saving a lead may also save its current company in Sales Navigator. Optional string ID, never a number. Eligible: owned custom lead lists; other targets return listNotFound. Current limitation: If you have more than 10 lead lists, Sales Navigator shows ten lists at a time. If the requested list is not shown, the call fails with unexpectedError. The lead may already be saved, but not added to that list. Sales Navigator can take up to a few minutes to reflect a change. A call that conflicts with a change you just made through Linked API may fail with unexpectedError; retry it a little later. Returns a workflow acknowledgement; use get_workflow_result with operationName nvSaveLead. Success has no result data.

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_save_lead"
  }
}

Input Schema

Name	Required	Description	Default
`listId`	No	Optional string ID, never a number. Eligible: owned custom lead lists; other targets return listNotFound. Current limitation: If you have more than 10 lead lists, Sales Navigator shows ten lists at a time. If the requested list is not shown, the call fails with unexpectedError. The lead may already be saved, but not added to that list.
`personHashedUrl`	Yes	URL accepted by nv.openPersonPage, including nv.retrieveAlerts subject.url.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Far exceeds the annotations (readOnlyHint=false, openWorldHint=true): it discloses idempotent replay behavior, the side effect of also saving the current company, the ten-list visibility limitation that produces unexpectedError, eventual-consistency delay of minutes, and conflict/retry guidance. It also explains the queued workflow model, the pendingReason values ('queued' vs 'outsideWorkingHours'), and instructs the agent to report the working-hours case instead of looping.

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?

The tool-specific opening is well front-loaded and every sentence there earns its place, but the trailing two paragraphs about queued workflows, pendingReason, and working hours are generic server-wide boilerplate that inflates the definition substantially. The essential warnings (don't retry, poll via get_workflow_result) are correct but could be compressed.

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?

With no output schema, the description carries the return-value burden and does so well: it states the acknowledgement shape, the operationName to poll with, and that success carries no result data. The only gap is that the meaning of the personHashedUrl input is left entirely to the schema's cross-reference to nv.openPersonPage.

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 listId description is repeated almost verbatim from the schema, so most parameter meaning is already structured data. The description does add one genuine semantic nuance — that listId ensures membership in that single list while leaving other lists unchanged — but that leans more toward behavior than parameter meaning.

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 concrete verb and resource ("Ensure a lead is saved") plus the exact conditional scope ("with listId, also ensure membership in that one list, leaving other lists untouched"). The idempotency clause ("Repeating succeeds without changes") and the "Plus-only root action nv.saveLead" identifier let an agent distinguish this from nv_save_account and nv_remove_lead_from_list without opening any schema.

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 use conditions for both branches (with listId vs. without listId) and exclusion rules (only owned custom lead lists are eligible; other targets return listNotFound). It also mandates the follow-up path ("use get_workflow_result with operationName nvSaveLead") and warns against retrying while a workflow runs. It stops short of naming sibling tools an agent should pick instead, so 4 rather than 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.