LeadMarina

Estimate an advanced search

estimate_advanced_search

Read-onlyIdempotent

What an advanced search (many keywords across many places) would find and how long it would take — without starting it or spending anything. expected_leads is the most likely number of unique leads (each business is charged once however many keywords or places find it); low–high is the range it lands in most of the time.

Input Schema

Name	Required	Description
`name`	No	Optional name, up to 80 characters.
`places`	No	Single places by name ('Austin'), 'name, region' when a name is in several ('Springfield, Illinois'), or code (find_places). Up to 25,000 regions and places together; keywords × places may come to at most 50,000 searches.
`country`	No	'US' (the default), or a US territory's code ('PR', 'GU', 'VI', 'AS', 'MP') with a place from find_places.
`regions`	No	Whole US states, by name or code (find_places).
`keywords`	Yes	What to search for: up to 20 keywords or Google categories, each up to 100 characters. Each a string, or { keyword, exact } where exact keeps only businesses whose main Google category is that one.
`lead_cap`	No	Stop after this many unique, charged leads: a whole number from 100 to 1,000,000. Omit to search every place.
`everywhere`	No	Every place in the US (or in the territory sent as country).

Output Schema

Name	Required	Description
`low`	No
`high`	No
`time`	No	How long it would take, waits for the daily city budget included.
`places`	No
`country`	No
`keywords`	No	Each { keyword, exact }, as they would run.
`searches`	Yes	Keywords × places.
`next_step`	No
`charged_leads`	No	Leads expected to be charged: expected_leads, capped by lead_cap.
`expected_leads`	Yes
`paced_by_daily_budget`	No	True when the account's daily city budget, not the searching, sets the time.
`campaign_searches_per_day`	No	Places a day advanced searches may use on this plan.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: nothing is started and nothing is spent, i.e., a free preview — a cost trait annotations cannot express. It stops short of noting any rate limits or latency expectations.

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?

Two sentences, the cost-free preview claim front-loaded, and the return-value semantics confined to one follow-up sentence. No filler and nothing repeated from the schema.

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?

With an output schema present and 100% parameter coverage, the definition covers what an agent needs to call it: it is a non-executing, non-charging estimator. It could still note whether an estimate must precede run_advanced_search or how stale an estimate becomes, but nothing essential is missing.

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 every parameter is already documented, and the description adds no syntax or format detail beyond that. It does clarify the lead accounting model ("each business is charged once however many keywords or places find it"), which gives useful context for lead_cap, but that is marginal against a fully described schema.

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?

Specific verb (estimate) plus resource (an advanced search), with the scope spelled out: "What an advanced search (many keywords across many places) would find and how long it would take." The clause "without starting it or spending anything" cleanly separates it from run_advanced_search and control_advanced_search.

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 phrase "without starting it or spending anything" clearly signals the when: a dry-run check before committing. However, no sibling is named explicitly — an agent has to infer that run_advanced_search is the follow-up, and there are no stated preconditions or exclusions.

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

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.