Save a LinkedIn Sales Navigator lead to a specified list using its profile URL. Organize leads into lists for efficient pipeline management.
Save a lead to a list on LinkedIn Sales Navigator
| Name | Required | Description | Default |
|---|---|---|---|
| listName | No | Name of the list to save to (default: saved leads) | |
| profileUrl | Yes | Sales Navigator profile URL of the lead to save |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'save a lead to a list' without mentioning side effects, whether the list must already exist, authentication requirements, or whether the operation is idempotent. This leaves significant behavioral uncertainty for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the core action and target. It contains no redundant information and is easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (2 parameters, one required) and the absence of an output schema, the description provides a minimal but functional overview. However, it lacks context about the relationship to list management tools (e.g., whether the list is created automatically) and does not clarify default behaviors, leaving gaps for an agent to infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters documented clearly in the input schema. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'save' with a clear object 'lead' and destination 'list on LinkedIn Sales Navigator', making the tool's function immediately clear. It distinguishes itself from sibling tools like search, profile retrieval, or list creation by focusing on the save action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used for persisting a lead to a list, but it does not explicitly state when to use it over alternatives such as linkedin_create_lead_list for creating a new list or linkedin_export_leads for bulk operations. No exclusionary guidance is provided, so usage context is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.