Skip to main content
Glama
Sign In

Linked API

by io.github.Linked-API
OverviewDiscussionsAdmin

nv_unsave_lead

Plus-only root action nv.unsaveLead. Use Sales Navigator's native unsave: the lead is no longer saved and leaves every custom list the user owns. 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 nvUnsaveLead. 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_unsave_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
personHashedUrlYesURL accepted by nv.openPersonPage, including nv.retrieveAlerts subject.url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only state readOnlyHint=false and openWorldHint=true; the description adds substantial context beyond them — idempotency ('repeating succeeds without changes'), several-minute propagation lag, conflict/retry behavior with unexpectedError, the queued-workflow model, the pendingReason values and what each means operationally, and the duplicate-work warning. This is more than the annotations could ever 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 and consequences are front-loaded in the first two sentences, which is good, but roughly half the text is generic workflow/pendingReason boilerplate that appears to be shared across sibling tools rather than specific to unsaving a lead. It is organized and not confusing, but it is longer than this tool's own behavior requires.

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 queued write action with no output schema, the description covers what is returned (a workflow acknowledgement with no result data), how to obtain the final result, and how to interpret parked or queued states. Nothing an agent needs to call and follow up correctly is missing.

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% and the tool has a single required param, so the schema already carries personHashedUrl semantics, including the cross-reference to nv.openPersonPage. The description adds nothing about the parameter, 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?

The description names a specific verb and resource ('unsaveLead', 'no longer saved') and states the scope consequence — the lead leaves every custom list the user owns — which is exactly what distinguishes it from the sibling nv_remove_lead_from_list. An agent can select it without opening the 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?

It gives clear usage context: use Sales Navigator's native unsave, retry later on unexpectedError conflicts, and route to get_workflow_result with operationName nvUnsaveLead for the outcome. It stops short of explicitly saying when to prefer nv_remove_lead_from_list or nv_save_lead, though the 'leaves every custom list' line implicitly covers that contrast.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Linked API toolsInspect
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.

Resources