Skip to main content
Glama

nv_save_account

Plus-only root action nv.saveAccount. Ensure an account is saved; with listId, also ensure membership in that one list, leaving other lists untouched. Without listId, leave lists unchanged. Repeating succeeds without changes. Optional string ID, never a number. Eligible: owned custom account lists or My Current Accounts; other targets return listNotFound. Current limitation: If you have more than 10 account lists, Sales Navigator shows ten lists at a time. If the requested list is not shown, the call fails with unexpectedError. The account may already be saved, but not added to that list. 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 nvSaveAccount. 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_save_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdNoOptional string ID, never a number. Eligible: owned custom account lists or My Current Accounts; other targets return listNotFound. Current limitation: If you have more than 10 account lists, Sales Navigator shows ten lists at a time. If the requested list is not shown, the call fails with unexpectedError. The account may already be saved, but not added to that list.
companyHashedUrlYesURL accepted by nv.openCompanyPage, including nv.retrieveAlerts subject.url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true) by disclosing async queueing, the immediate {status, pendingReason, workflowId} acknowledgement, the queued vs outsideWorkingHours distinction, minutes-scale propagation delay, and an explicit no-retry-while-running warning against duplicate queued work. The 10-list visibility limitation and its unexpectedError outcome are concrete behavioral caveats an agent would otherwise have no way to know.

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?

Front-loaded with the operation's core semantics before the async-mechanics boilerplate, which is the right ordering. It is long and duplicates the listId constraint text from the schema, plus the generic workflow paragraph is shared boilerplate, but nearly every sentence carries actionable constraint information.

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 full return contract: a workflow acknowledgement with status/pendingReason/workflowId/operationName, and the instruction to call get_workflow_result with operationName nvSaveAccount. Success-has-no-result-data is stated, so nothing an agent needs to interpret the response 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 coverage is 100%, and the listId paragraph in the description is nearly verbatim what the schema property already states, so little meaning is added. The description does reinforce that listId is always a string and never a number, but companyHashedUrl is not elaborated beyond the schema.

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?

Names a specific verb and resource ('Ensure an account is saved') and precisely delineates scope: with listId it also ensures membership in that single list, without listId it leaves lists untouched. This clearly separates it from nv_unsave_account and nv_remove_account_from_list without requiring schema inspection.

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 strong when-to-use context: eligibility (owned custom account lists or My Current Accounts), the failure mode for other targets (listNotFound), idempotent retry semantics ('Repeating succeeds without changes'), and a conflict/retry rule. It stops short of explicitly naming sibling alternatives such as nv_retrieve_lists for discovering a listId or nv_remove_account_from_list for the inverse operation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.