leadmarina

Query the lead library

query_leads

Read-only

Search ALL leads the account has ever collected (across every search) with filters and sorting — no new search is run and no leads are spent. Filter fields include: name, category, city, state, rating, reviews, website, claimed, owner_name, phone_1, email_1, email_1_status, phone_1_type, google_cid. Operators: contains, not_contains, is, is_not, starts_with, gt, gte, lt, lte, is_empty, is_not_empty, is_true, is_false. Combine rows with conj 'and'/'or'. Example: find rated-4.5+ plumbers in Austin with a verified email: filters=[{field:'category',operator:'contains',value:'plumb'},{field:'city',operator:'is',value:'Austin',conj:'and'},{field:'email_1_status',operator:'is',value:'safe',conj:'and'}].

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort keys, e.g. [{id:'reviews',dir:-1}]. Optional.
`limit`	No	Max leads to return (default 25, max 1000).
`cursor`	No	Opaque pagination cursor from a previous call.
`filters`	No	Filter conditions (optional — omit for everything, newest data first).

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes
`returned`	Yes
`next_cursor`	No	Pass back as 'cursor' for the next page.
`total_matching`	No	Exact match count (first page only; absent on later pages).

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable context by stating 'no new search is run and no leads are spent', which discloses the cost/impact behavior beyond the annotations. It also details filter operators and behavior, providing deep transparency.

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 front-loaded with the core message, then provides detailed operator lists and a practical example. Every sentence contributes essential usage information, and the structure is efficient for a tool with complex filtering logic.

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?

For a tool with complex filtering and sorting, the description covers the most important behavioral aspects comprehensively. The presence of an output schema means return values need not be explained, and the description fully addresses the tool's unique value proposition.

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

Parameters5/5

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

Although schema coverage is 100%, the description elevates parameter understanding by enumerating all filterable fields, supported operators, conjunction semantics, and a concrete example. This goes far beyond the schema's bare parameter definitions.

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?

The description clearly states the tool searches ALL leads the account has ever collected, distinguishing it from search_leads by noting it does not run a new search. The verb 'Search' and resource 'lead library' make the purpose explicit and unambiguous.

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?

The description explicitly states that no new search is run and no leads are spent, which implicitly guides when to use this tool versus search_leads. It does not name the alternative tool directly, but the context is clear and it includes a concrete example of usage.

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

All leadmarina tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a distinct purpose: search_leads runs live searches while query_leads filters collected leads; create/delete/update_automation form a clear lifecycle; list_* tools target different resources. Descriptions explicitly disambiguate potential overlaps like search/query and list_searches/list_views.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., create_automation, list_integrations, export_leads). The verbs are semantically appropriate (get, list, search, query, create, update, delete, enrich, export) and the pattern is uniform throughout.

Tool Count5/5

13 tools is well within the ideal range and covers the full lead-generation workflow without redundancy. Each tool addresses a concrete need, from searching and enrichment to export and automation management.

Completeness5/5

The tool set covers the entire lifecycle: search_leads and enrich_domains acquire leads, get_search_results and query_leads retrieve them, export_leads pushes them out, and automations re-run searches on schedule. Integration checking and balance are also included, leaving no obvious dead ends or missing essential operations.

Resources

Need Help?