Linked API

nv_create_saved_search

Save a Sales Navigator search URL matching the requested type. Returns its id, name, type and URL. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvCreateSavedSearch.

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>",
      "customSearchUrl": "<customSearchUrl>"
    },
    "name": "nv_create_saved_search"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes	Sales Navigator subject type.
`customSearchUrl`	Yes	Sales Navigator search URL copied from /sales/search/people for lead or /sales/search/company for account; must match type.

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=false and openWorldHint=true annotations, the description discloses that the action is queued into a cloud-browser workflow, may take minutes, returns an immediate pending snapshot, and distinguishes pendingReason 'queued' from 'outsideWorkingHours' with the correct agent behavior for each. It also flags the duplicate-work hazard of retrying, which is exactly the kind of behavior an agent cannot infer from structured fields.

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 core purpose and return shape are front-loaded in the first sentence, followed by prerequisites, the correct follow-up call, and then the async workflow semantics. The workflow explanation is long and partly overlaps between the second and third paragraphs, but each piece carries operational value 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 supplies the return shape (id, name, type, URL) and fully explains the asynchronous envelope plus how to resolve it. For an open-world, queued mutation tool this covers everything an agent needs to call it and handle the result correctly.

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 both parameters are fully documented there, including the type/customSearchUrl matching constraint, so the baseline is 3. The description adds only the 'matching the requested type' reinforcement and the English-interface constraint, no new per-parameter meaning beyond the schema.

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 ('Save a Sales Navigator search URL matching the requested type') and names what it returns (id, name, type, URL), which separates it from nv_retrieve_saved_searches and nv_delete_saved_search. It stops short of explicitly naming those siblings as alternatives, so it is clear but not maximally differentiated.

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 concrete prerequisites ('English interface only. Plus required.') and prescribes the exact follow-up path via get_workflow_result with operationName nvCreateSavedSearch. It also warns not to retry while a workflow is running, which is a real usage rule; what is missing is guidance on when a search should be saved at all versus just re-run with nv_search_people/nv_search_companies.

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.