Funkel AI

search_external_leads

Search LinkedIn for fresh people leads from the request user's connected account. Use this when the user describes leads to find by words, roles, companies, or market terms, rather than asking to search existing saved leads. Returns a server-owned session_id and up to 10 lead previews. To import the results, call import_search_leads_to_list with that session_id after the user asks to import all or selected leads. Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_external_leads"
  }
}

Input Schema

Name	Required	Description
`role`	No	Optional job-title filter, e.g. 'Founder OR CEO'
`limit`	No	Max results to return (1..10). Default 10.
`query`	Yes	Free-text people search, e.g. 'YC founders building AI devtools'

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true and non-idempotent, and the description adds real context beyond them: it runs immediately, needs no confirmation_token over MCP, and returns a server-owned session_id plus at most 10 previews. It does not explain why readOnlyHint=false for what reads as a search, nor any rate limits, leaving a small gap.

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?

Front-loaded with the core purpose, then the usage condition, the return shape, the import handoff, and the MCP calling convention. Every sentence carries information, though the closing 'It runs right away and returns the result' partly restates the preceding sentence.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so by naming the session_id and the up-to-10 lead previews. Combined with the import handoff and MCP invocation note, an agent has everything needed to call and follow up correctly.

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 query, role, and limit are already documented with examples and bounds. The description's phrase 'words, roles, companies, or market terms' loosely maps to query/role but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (Search), a specific resource (LinkedIn fresh people leads), and the scope (from the request user's connected account). It also distinguishes itself from searching existing saved leads, so an agent can tell it apart from siblings like find_leads and list_list_contacts without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the trigger condition ('when the user describes leads to find by words, roles, companies, or market terms') and the exclusion ('rather than asking to search existing saved leads'). It also routes the follow-up step to import_search_leads_to_list with the returned session_id, giving a complete when-to-use chain.

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

All Funkel AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?