Linked API

nv_send_message

Allows you to send a message to a person in Sales Navigator (nv.sendMessage action). Provide either personUrl or threadId (threadId replies into an existing conversation thread and takes precedence). If this workflow is still running, do not retry this tool; retrying can send duplicate Sales Navigator messages to the same person.

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": {
      "text": "<text>"
    },
    "name": "nv_send_message"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The message text, must be up to 1900 characters.
`subject`	No	Subject line, must be up to 80 characters. Required when starting a new conversation; ignored when replying into an existing thread via threadId.
`threadId`	No	Optional conversation thread identifier to reply into, as returned by get_inbox. Provide this instead of personUrl to reply directly into a known thread.
`personUrl`	No	LinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe'). Optional if threadId is provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The annotations only say readOnlyHint=false and openWorldHint=true; the description adds substantially more, explaining that the call is queued into a cloud-browser workflow, returns immediately with a pending snapshot (workflowId, operationName, pendingReason), and can take minutes. It also flags the duplicate-message risk from retrying and explains the 'queued' and 'outsideWorkingHours' pending reasons, which an agent could not infer from the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The message opens with the addressing rule, so the most error-prone decision comes first. It is three paragraphs long, but each one adds information the agent needs, apart from a small repetition of the 'do not retry' warning between the first and second paragraphs.

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, so the description covers the return shape itself: a pending snapshot with status, pendingReason, workflowId and operationName, plus how to resolve it. Together with the duplicate-risk and working-hours caveats, an agent has everything it needs to call the tool and handle the result correctly.

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 already 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the mutual exclusivity of personUrl and threadId and the rule that threadId takes precedence and suppresses the subject line. That precedence rule is the kind of constraint an agent can easily get wrong if it only reads 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 ('send a message to a person in Sales Navigator') and names the underlying action (nv.sendMessage). It clarifies the two addressing modes (personUrl vs threadId) but never mentions the generic sibling send_message, so an agent cannot tell from this text alone why it should pick nv_send_message over it.

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 routing rules: supply either personUrl or threadId, threadId takes precedence and replies into an existing thread. It also tells the agent to stop and use get_workflow_result instead of retrying. The gap is that it offers no guidance on nv_send_message vs the sibling send_message or nv_manage_conversation.

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.