Linked API MCP

nv_send_message

Send a direct message to a LinkedIn Sales Navigator contact by providing their profile URL, a subject line, and the message text.

Instructions

Allows you to send a message to a person in Sales Navigator (nv.sendMessage action)

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

Input Schema

Name	Required	Description
`personUrl`	Yes	LinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe')
`text`	Yes	The message text, must be up to 1900 characters.
`subject`	Yes	Subject line, must be up to 80 characters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 23, 2025

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description fails to disclose any behavioral traits such as authentication requirements, rate limits, or side effects. It only states the action, leaving the agent uninformed about important behavioral aspects.

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 description is a single, front-loaded sentence that efficiently communicates the core purpose. It is concise, though it could include more detail without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 required params, no output schema, no annotations), the description is too minimal. It omits crucial context such as prerequisites, success/failure behavior, or any constraints beyond character limits.

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% with clear descriptions for each parameter (personUrl, text, subject). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 description clearly states the action ('send a message') and the resource ('a person in Sales Navigator'), effectively distinguishing it from the generic sibling tool 'send_message' by specifying the Sales Navigator context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'send_message' or other messaging-related tools. The description lacks context for when to choose it over siblings.

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