Linked API

nv_unsave_account

Plus-only root action nv.unsaveAccount. Unsave the account only; its saved leads stay saved. Repeating succeeds without changes. 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 nvUnsaveAccount. 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": {
      "companyHashedUrl": "<companyHashedUrl>"
    },
    "name": "nv_unsave_account"
  }
}

Input Schema

Name	Required	Description	Default
`companyHashedUrl`	Yes	URL accepted by nv.openCompanyPage, including nv.retrieveAlerts subject.url.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, open-world mutation, so the safety profile is covered; the description adds genuine value with idempotency ("repeating succeeds without changes"), propagation latency of a few minutes, and the conflict/retry behavior. It also discloses the acknowledgement-only return shape and the meaning of pendingReason values ('queued' vs 'outsideWorkingHours').

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?

The tool-specific material is front-loaded in the first paragraph and is dense with real constraints. The workflow/pending boilerplate that follows is long and generic, but it does carry invocation-critical detail (polling semantics, pendingReason meanings) rather than filler.

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?

With no output schema, the description fully accounts for the return value: a workflow acknowledgement with status/workflowId, no result data on success, and the exact follow-up call needed to obtain completion. Pending and outside-working-hours states are explained, so an agent knows what to report instead of looping.

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 parameter's description already points at nv.openCompanyPage and nv.retrieveAlerts subject.url. The prose never mentions companyHashedUrl or adds format/source detail beyond the schema, 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 ("nv.unsaveAccount") plus the exact scope boundary: "Unsave the account only; its saved leads stay saved." That boundary alone separates it from nv_unsave_lead and its inverse nv_save_account without needing either 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?

Explains what to do after calling (poll via get_workflow_result with operationName nvUnsaveAccount), warns not to retry the original tool while a workflow is running, and covers the conflict case ("a call that conflicts with a change you just made through Linked API may fail with unexpectedError; retry it a little later"). It stops short of explicitly naming nv_save_account as the counterpart or stating prerequisites for Plus accounts.

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.