Linked API

nv_create_list

Plus-only root action nv.createList. Create an owned lead or account list. Name is trimmed (1–75 characters). Optional description has surrounding spaces trimmed, allows up to 350 characters after trimming, and is omitted when blank. Same-type names equal after trimming, case-sensitive, including system lists, return listAlreadyExists and create nothing. Final data is { id: string, name, type, url }. English interface only; errors also include interfaceLanguageNotSupported, noSalesNavigator and unexpectedError. Returns a workflow acknowledgement; use get_workflow_result with operationName nvCreateList.

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

Input Schema

Name	Required	Description
`name`	Yes	Name, trimmed; 1–75 characters after trimming.
`type`	Yes	Owned list type to create.
`description`	No	Optional description; surrounding spaces are trimmed. Up to 350 characters after trimming; blank omitted.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond readOnlyHint=false and openWorldHint=true, the description discloses duplicate-collision behavior (same-type names equal after trimming, case-sensitive, including system lists), the listAlreadyExists failure mode, English-only support with named error codes, the final payload shape, and the full queued-workflow lifecycle including pendingReason values.

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 purpose is front-loaded and the workflow model is genuinely necessary, but the name and description trimming rules restate the schema almost verbatim, and the generic queued-workflow and working-hours paragraphs are long boilerplate that inflates the definition without tool-specific value.

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, and the description compensates by stating the final data shape ({ id, name, type, url }) and the interim acknowledgement shape, then routing the agent to get_workflow_result with the right arguments. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents trimming and length bounds, so the baseline is 3. The description earns a point by explaining what the schema cannot: case-sensitive, post-trim equality against existing lists of the same type, including system lists, which determines whether creation proceeds at all.

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 first sentence gives a specific verb and resource ('Create an owned lead or account list') with the enum values spelled out. It is easy to separate from siblings such as nv_rename_list, nv_delete_list, and nv_retrieve_lists, whose names imply different operations.

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 clearly establishes the creation use case and adds operational guidance: do not retry while a workflow is running, and instead call get_workflow_result with the workflowId and operationName. It does not name alternatives for related tasks (e.g., nv_retrieve_lists to verify existing lists, nv_save_lead to populate them), so the sibling routing is only partially addressed.

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.