MightyAutomation

Search leads & contacts

search_leads

Read-onlyIdempotent

Search the CRM by free text (matches first/last name, email, company), pipeline stage, lifecycle (lead|prospect|contact|customer|churned), or "has a phone number". Returns matching contacts and a total.

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
`q`	No	Free-text search across name, email, and company.
`limit`	No	Max results, 1-200 (default 50).
`stage`	No	Pipeline stage name — exact match. Get stage names from list_pipeline_stages.
`offset`	No	Rows to skip for paging (default 0).
`has_phone`	No	true → only contacts with a phone number.
`lifecycle`	No	Lifecycle filter.

Output Schema

Name	Required	Description
`ok`	No
`error`	No	Present only when ok is false.
`leads`	No
`total`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to reiterate that. It adds that results include matching contacts plus a total, but does not disclose permissions, rate limits, or other behavioral traits beyond what annotations and schema already provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states the searchable dimensions first and the return shape second. There is no filler, and every clause contributes to understanding the tool.

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?

Given full schema coverage, comprehensive read-only annotations, and an output schema, the description contains enough context to call this search tool correctly. Pagination and exact stage-name lookup are left to the schema, which is appropriate because those details are already documented there.

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 the schema already documents all six parameters. The description restates the main filter categories and slightly clarifies that free text matches first/last name, email, and company, but most parameter meaning comes from the schema rather than the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: search the CRM for contacts/leads. It also names the supported filter dimensions and the return shape, so the tool's purpose is clear. It does not explicitly distinguish itself from sibling tools such as find_contact or list_contacts, which keeps it from a 5.

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

Usage Guidelines2/5

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

The description explains what can be searched but gives no explicit guidance on when to use this tool versus find_contact, list_contacts, or get_contact. There are no exclusions or alternative-routing instructions in the description.

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

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