Skip to main content
Glama
artik0din

MCP LinkedIn Sales Navigator

by artik0din
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_save_lead

Save a LinkedIn Sales Navigator lead to a specified list, with a dry-run option to preview the action before committing.

Instructions

Save a lead to a list on LinkedIn Sales Navigator. Always preview first with dryRun=true before saving (default dryRun=false preserves prior behaviour).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, locate the save UI with human-like pacing but do not click Save (preview only). Prefer true before a real save.
listNameNoName of the list to save to (default: saved leads)
profileUrlYesSales Navigator profile URL of the lead to save

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": false,
+  "description": "If true, locate the save UI with human-like pacing but do not click Save (preview only). Prefer true before a real save.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that dryRun previews without clicking and that default is false (actual save), which is a key behavioral trait. However, it omits other relevant behaviors such as prerequisites (e.g., active session), potential side effects, or error handling, leaving the agent with partial transparency.

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 description is extremely concise—two sentences—and front-loads the core action before the cautionary note. Every word earns its place, and the instruction is placed after the purpose for clarity.

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

Completeness3/5

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

For a tool with three parameters, no output schema, and no annotations, the description is adequate but leaves gaps: it doesn't clarify whether the list must already exist, what happens on failure, or if authentication is required. The guidance to preview mitigates some risk, but the agent may still lack sufficient context for correct invocation.

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%, so all parameters already have descriptions. The tool description repeats the dryRun default and intent but adds no meaning beyond the schema. The baseline of 3 applies because the schema does the heavy lifting and the description contributes no extra parameter context.

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 states a specific verb ('Save') and resource ('a lead to a list on LinkedIn Sales Navigator'), clearly distinguishing it from sibling tools like search, export, or profile retrieval. The purpose is unambiguous and immediately actionable.

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

Usage Guidelines3/5

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

The description provides a strong operational guideline ('Always preview first with dryRun=true before saving') but does not explicitly contrast this tool with alternatives or state when not to use it. It implies the tool's role relative to siblings but leaves the selection logic to the agent.

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

Deploy Server

Other Tools