search_leadsFind and scrape LinkedIn lead details using advanced filters to target specific prospects.
Find and scrape lead details with advanced filters.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_leads"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must disclose behavior. It mentions 'scrape' implying some data-fetching behavior, but does not state whether it is read-only, what data is returned, if it is expensive, or whether authentication is required. The phrase 'advanced filters' is misleading because no filter parameters are exposed in the schema.
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 one short sentence, which is concise, but it front-loads a claim ('advanced filters') that is unsupported. Conciseness is not a virtue when it omits essential information. It earns a 3 because it is brief but not effectively structured.
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?
With no annotations, no parameters, and no output schema, the description is the only source. It fails to explain what 'lead details' are, how filters work (or that there are none), what the return format is, or any operational constraints. Completely inadequate for a tool with this many siblings.
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?
The schema defines zero parameters, yet the description claims 'advanced filters'. This is a direct contradiction: the agent cannot supply any filters, so the description adds misleading meaning rather than clarifying the schema. Baseline 4 for zero parameters is overridden because the description actively misrepresents the tool's capabilities.
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 states a clear verb and resource ('Find and scrape lead details'), but 'advanced filters' is vague and there is no indication of what distinguishes this from the many sibling search tools like search_leads_v2, lead_search_at_scale, or search_decision_makers. The purpose is partially clear but lacks specificity around scope and output.
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 the numerous siblings. There is no mention of context, prerequisites, or alternatives. The description does not help an agent decide between this and search_leads_v2.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.