Create a new lead list in LinkedIn Sales Navigator to organize and manage leads for targeted outreach.
Create a new lead list in LinkedIn Sales Navigator
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name for the new lead list |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, authentication needs, duplicate handling, or return behavior. For a mutating operation, this lack of detail is insufficient.
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, front-loaded sentence with no redundant words. It is appropriately sized for a simple creation tool with one parameter, conveying the core purpose efficiently.
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?
The description covers the basic purpose but lacks usage guidelines and behavioral transparency. Given no output schema and no annotations, it is minimally adequate for a simple one-parameter tool, but an agent would benefit from knowing return values or constraints to ensure correct invocation.
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% for the 'name' parameter, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, but the schema fully documents the parameter, so no extra compensation is needed.
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 clearly states the action ('create') and the resource ('new lead list') with platform context ('in LinkedIn Sales Navigator'). It distinguishes this from sibling tools like list_lead_lists and save_lead by explicitly targeting creation of a new list.
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?
No guidance is provided on when to use this tool versus alternatives such as linkedin_save_lead or linkedin_list_lead_lists. The description offers no context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.