Linked API

nv_remove_account_from_list

Remove an account from exactly one owned custom list, keeping it saved even after its last list. Repeating an absent membership succeeds. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRemoveAccountFromList.

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

Input Schema

Name	Required	Description	Default
`listId`	Yes	Owned list ID as a string, never a number.
`companyHashedUrl`	Yes	Public or hashed LinkedIn company URL, including /company/... and /sales/company/... or an alert subject URL.

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?

The description goes well beyond the annotations, which only say readOnlyHint=false and openWorldHint=true. It discloses that the action is queued into a cloud-browser workflow, that the server returns a pending/running snapshot immediately, the meaning of pendingReason 'queued' vs 'outsideWorkingHours', that retrieval long-polls, and that retrying during a run creates duplicate work. It also flags the Plus plan and English-only constraints.

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 purpose and its key guarantee are front-loaded in the first sentence, and the structure moves logically from action to prerequisites to workflow handling. The workflow boilerplate is long and partially repetitive (get_workflow_result with operationName is stated twice), which keeps it from a 5.

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 only two well-documented parameters, no output schema, and async workflow behavior, the description covers everything an agent needs: prerequisites, idempotency, the return shape, the follow-up call, and how to interpret pending states. Nothing essential to correct invocation 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% for both parameters, so the semantics of listId and companyHashedUrl are already documented in the schema. The description adds the 'owned custom list' framing but no new format, validation, or edge-case detail for either parameter, so the baseline of 3 applies.

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: 'Remove an account from exactly one owned custom list,' and adds the non-obvious guarantee that the account stays saved after leaving its last list. The account-vs-lead distinction implicitly separates it from nv_remove_lead_from_list, but no sibling is named explicitly, so it falls short of a 5.

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 clear operating context: exactly one list per call, repeated removals of an absent membership succeed (idempotent), English interface only, and Plus plan required. It also tells the agent what to do after invocation (call get_workflow_result, do not retry while running). It stops short of explicitly naming alternatives such as nv_unsave_account for full removal.

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.