LeadsIt

Search my leads

search_leads

Read-only

Search the businesses this LeadsIt account has already found, best sales score first, with their emails, phones, websites and social profiles. Put every filter in one call; the result has the total that match. Use offset to page. format "csv" returns a CSV file of up to 5,000 rows for a spreadsheet. Free.

Tool call template

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"
  }
}

Input Schema

Name	Required	Description
`city`	No	City or place name
`limit`	No	Rows to return: 1-100 as JSON (default 25), up to 5000 as CSV
`stage`	No	Only leads in this pipeline stage (plans with the CRM)
`format`	No	json (default) or csv
`offset`	No	Rows to skip, for the next page
`hasEmail`	No	Only businesses with an email
`hasPhone`	No	Only businesses with a phone number
`listName`	No	Only leads in this CRM list (plans with the CRM)
`minScore`	No	Minimum sales score
`searchId`	No	Only the leads of this search
`noWebsite`	No	Only businesses with no website of their own
`businessType`	No	Business type or category, e.g. "dentist", "restaurant", "web agency"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond them - default sort by sales score, a total-match count in the response, a 5,000-row CSV cap, and 'Free' (no credit cost) - but remains silent on rate limits, whether the total is exact, and CSV delivery mechanics.

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 and tightly written, with scope and sort order first and operational hints after. Minor redundancy: the CSV/5,000-row rule restates the schema, and the one-word 'Free.' sentence is useful but stylistically abrupt.

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

Completeness4/5

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

For a 12-parameter, zero-required query tool with no output schema, it covers retrieval scope, ordering, paging, result totals, and the CSV alternative format - enough to call it correctly. Remaining gaps are secondary: exact pagination termination and whether filters combine with AND semantics are only implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point for clarifying that all filters are conjoined in a single call and by tying offset/limit to paging behavior. Some overlap exists, since the CSV/5,000-row distinction is already in the limit and format schema descriptions.

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 and resource ('Search the businesses this LeadsIt account has already found') and pins the scope to already-discovered leads, which implicitly separates it from create_lead_search. It also names the returned fields (emails, phones, websites, social profiles) and the sort order (best sales score first), so an agent knows exactly what it gets.

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

Usage Guidelines4/5

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

Gives concrete invocation guidance: combine all filters in one call, use offset to page, and use format="csv" for spreadsheet export. It stops short of naming the alternative path for discovering new businesses (create_lead_search), which would have made the when-not case explicit.

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

All LeadsIt 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?