Skip to main content
Glama
Linked-API
by Linked-API

nv_send_message

Send personalized messages to LinkedIn Sales Navigator contacts using their profile URL, subject line, and message text.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personUrlYesLinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe')
textYesThe message text, must be up to 1900 characters.
subjectYesSubject line, must be up to 80 characters.

Implementation Reference

  • Core implementation of the 'nv_send_message' tool as NvSendMessageTool class, including name, operation mapping, Zod schema for validation, and MCP Tool descriptor via getTool().
    export class NvSendMessageTool extends OperationTool<TNvSendMessageParams, unknown> {
      public override readonly name = 'nv_send_message';
      public override readonly operationName = OPERATION_NAME.nvSendMessage;
      protected override readonly schema = z.object({
        personUrl: z.string(),
        text: z.string().min(1),
        subject: z.string().optional(),
      });
    
      public override getTool(): Tool {
        return {
          name: this.name,
          description:
            'Allows you to send a message to a person in Sales Navigator (nv.sendMessage action)',
          inputSchema: {
            type: 'object',
            properties: {
              personUrl: {
                type: 'string',
                description:
                  "LinkedIn URL of the person you want to send a message to (e.g., 'https://www.linkedin.com/in/john-doe')",
              },
              text: {
                type: 'string',
                description: 'The message text, must be up to 1900 characters.',
              },
              subject: {
                type: 'string',
                description: 'Subject line, must be up to 80 characters.',
              },
            },
            required: ['personUrl', 'text', 'subject'],
          },
        };
      }
    }
  • Instantiation and registration of NvSendMessageTool instance into the LinkedApiTools collection.
    new NvSendMessageTool(progressCallback),
  • Base OperationTool class providing the execute method, which is the handler logic for all operation-based tools including nv_send_message, by mapping to LinkedAPI operation and executing with progress tracking.
    export abstract class OperationTool<TParams, TResult> extends LinkedApiTool<TParams, TResult> {
      public abstract readonly operationName: TOperationName;
    
      public override execute({
        linkedapi,
        args,
        workflowTimeout,
        progressToken,
      }: {
        linkedapi: LinkedApi;
        args: TParams;
        workflowTimeout: number;
        progressToken?: string | number;
      }): Promise<TMappedResponse<TResult>> {
        const operation = linkedapi.operations.find(
          (operation) => operation.operationName === this.operationName,
        )! as Operation<TParams, TResult>;
        return executeWithProgress(this.progressCallback, operation, workflowTimeout, {
          params: args,
          progressToken,
        });
      }
    }
  • Zod schema for input validation of nv_send_message tool parameters.
    protected override readonly schema = z.object({
      personUrl: z.string(),
      text: z.string().min(1),
      subject: z.string().optional(),
    });
  • MCP server method that registers all tools, including nv_send_message, by exposing their Tool descriptors.
    public getTools(): Tool[] {
      return this.tools.tools.map((tool) => tool.getTool());
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral context. It mentions the Sales Navigator context but doesn't disclose critical traits like rate limits, permission requirements (e.g., Sales Navigator subscription), whether it's idempotent, or what happens on success/failure. The agent must infer this is a mutation from 'send'.

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, efficient sentence that front-loads the core purpose. The parenthetical about the action name is slightly redundant but not wasteful. It could be slightly more structured but earns its place.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral constraints (e.g., rate limits, auth needs), expected outcomes, error conditions, and differentiation from siblings. The agent has insufficient context to use this tool safely and effectively.

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%, so parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying they're for Sales Navigator messaging. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the action ('send a message') and target ('to a person in Sales Navigator'), with the parenthetical clarifying it corresponds to the nv.sendMessage action. It distinguishes from the generic 'send_message' sibling by specifying the Sales Navigator context, though it doesn't explicitly contrast them.

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 is provided on when to use this tool versus the generic 'send_message' sibling or other communication tools like 'comment_on_post'. The description only states what it does, not when it's appropriate or what prerequisites exist (e.g., needing a connection or InMail credits).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Linked-API/linkedapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server