Crawdar Business Research

Server Details

Evidence-backed public business research for agents with compact, pageable output.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-11 23:16
Transport: Streamable HTTP
URL

TDQS

A4.3/5.0

Scored 2026-09-08 08:50 across 10 tools

Disambiguation4/5

Tools are mostly distinct, with clear separation between sync/async search, job lifecycle, review scanning, and sandbox testing. However, search_businesses, research_businesses, and start_lead_search all overlap in the core 'find businesses' use case and require careful reading of descriptions to pick correctly.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., start_lead_search, cancel_lead_search, scan_review_pain_points). The naming is predictable and clearly indicates the action being performed.

Tool Count5/5

Ten tools is a well-scoped set for a business research and lead search API. It covers sync and async workflows, lifecycle operations, documentation, review scanning, and testing without feeling bloated or sparse.

Completeness5/5

The tool set covers the full lead-search lifecycle: start, get, cancel, refine, retry, plus sync search, research, review pain points, sandbox testing, and explainer. There are no obvious missing operations for the stated domain.

Available Tools

10 tools

cancel_lead_searchCancel a lead searchA

DestructiveIdempotent

Inspect

Cancel a queued or running search job. Completed and failed jobs remain immutable.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Queued or running job id.
`jobToken`	Yes	Private token belonging to the job.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes
`status`	Yes
`canceledAt`	No

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint and idempotentHint. The description adds useful behavioral context: only queued or running jobs are affected, and completed/failed jobs are immutable, which clarifies why the operation is idempotent for terminal states.

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 deliver the action, the resource scope, and an important caveat without any filler. The main verb and target are front-loaded, making the purpose immediately clear.

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?

With an output schema present, both required parameters fully documented, and annotations covering safety profile, the description provides everything an agent needs to invoke cancellation appropriately. The immutability caveat covers edge cases of completed/failed jobs.

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?

The input schema provides full descriptions for both required parameters (id and jobToken) with 100% coverage. The description adds no additional parameter-specific meaning, so the baseline score of 3 is appropriate.

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 states a specific verb ('Cancel') and resource ('search job'), and further narrows scope to 'queued or running' jobs. This clearly distinguishes it from sibling tools like start_lead_search or get_lead_search.

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

Usage Guidelines3/5

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

The description implies when cancellation is valid by noting 'Completed and failed jobs remain immutable', which serves as a when-not. However, it does not explicitly name alternatives or direct the agent to a different tool for other job states.

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

explain_crawdarExplain Crawdar searchA

Read-onlyIdempotent

Inspect

Get result semantics, limits, interface URLs, and safe operating guidance. This tool does not consume a search.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`guidance`	Yes
`interfaces`	Yes
`resultLanes`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds a meaningful behavioral trait: 'does not consume a search.' This goes beyond the annotations by clarifying that the tool performs no search operation, which is important context. No contradiction with annotations.

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 concise sentences with no redundancy. The first sentence front-loads the core purpose, and the second adds a clarifying limitation. Every word earns its place, making it efficient and easy to parse.

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 zero parameters and an output schema, the description covers the essential information: what the tool returns (semantics, limits, URLs, guidance) and what it does not do (consume a search). An agent can confidently use this tool to obtain operational context for the search tools, and nothing critical is missing.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and the schema confirms no parameters exist. The description appropriately focuses on the tool's function rather than parameters.

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 states a specific purpose: to retrieve result semantics, limits, interface URLs, and safety guidance. It explicitly distinguishes itself from search operations with 'This tool does not consume a search.' This clearly differentiates it from the sibling search tools and gives an agent a precise understanding of what it does.

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 implies usage by stating what it provides and clarifying it does not consume a search. This sets a clear boundary versus the sibling search tools, though it doesn't explicitly state 'use this when you need to understand the search tool' or provide alternative conditions. The context is clear enough for an agent to infer when to use it.

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

get_lead_searchGet a lead search pageA

Read-onlyIdempotent

Inspect

Read job status or one cursor-paginated result page. Keep jobToken private and pass nextCursor back unchanged.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Job id returned by start_lead_search, refine_lead_search, or retry_lead_search.
`view`	No	Compact minimizes tokens. Full retains detailed evidence fields.	compact
`limit`	No	Maximum prospects in this result page.
`cursor`	No	Opaque nextCursor from the previous response.
`jobToken`	Yes	Private token returned with the job. Do not log or share it.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes
`error`	No
`status`	Yes
`results`	No
`progress`	No
`returned`	No
`warnings`	No
`createdAt`	No
`errorCode`	No
`nextCursor`	No
`retryAfter`	No
`completedAt`	No
`diagnostics`	No
`resultCount`	No
`searchedSources`	No

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the operation as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: the tool returns either job status or a paginated page, jobToken must be kept private, and cursor must be passed back unchanged. No contradiction with annotations exists.

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 short sentences front-load the core purpose and then give the two essential operational cautions. There is no filler or redundant restatement of the tool name.

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?

With an output schema present, annotations providing the safety profile, and full parameter documentation, the description supplies the missing high-level semantics: status/page duality, opaque cursor chaining, and token privacy. An agent has enough information to invoke it 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 coverage is 100%, and the schema already documents id provenance, view behavior, limit bounds, cursor opacity, and jobToken privacy. The description's 'keep jobToken private' and 'pass nextCursor back unchanged' largely echo schema text, with only the 'unchanged' nuance adding slight extra meaning.

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 states a specific verb ('Read') and resource ('job status or one cursor-paginated result page'). This clearly distinguishes it from sibling tools like start_lead_search, refine_lead_search, retry_lead_search, and cancel_lead_search, which create, modify, or cancel jobs rather than read results.

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 clearly frames the tool as a retrieval and pagination operation, and the instruction to pass nextCursor back unchanged gives concrete usage context. It does not explicitly name alternatives or exclusions, but the sibling tool set makes the retrieval-versus-creation contrast obvious.

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

refine_lead_searchRefine a lead searchAInspect

Create a new private search job by changing the brief or criteria of a completed job. The original job stays unchanged.

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Completed source job id returned by an earlier durable search call.
`brief`	No	Replacement natural-language brief for the new job.
`limit`	No	Maximum prospects retained by the new job.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`target`	No	Replacement business target for the new job.
`jobToken`	Yes	Private token belonging to the source job.
`geography`	No	Replacement city, region, country, or Worldwide.
`qualifier`	No	Replacement public requirements and exclusions.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Stable job identifier. Use it with jobToken in every lifecycle call.
`status`	Yes	Current durable job state.
`cacheHit`	No
`jobToken`	No	Private bearer token required to read, refine, or export this job.
`retryUrl`	Yes	Authenticated REST URL for creating a replacement after retryable failure.
`cancelUrl`	Yes	Authenticated REST URL for canceling queued or running work.
`exportUrl`	Yes	Authenticated CSV export URL. Add format=json for JSON.
`statusUrl`	Yes	Authenticated REST URL for job status and result pages.
`resultCount`	No
`expiresInSeconds`	Yes	Seconds until the private job and token expire.

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already indicate readOnly=false, destructive=false, and idempotent=false. The description adds that the original job remains unchanged, but it does not disclose persistence behavior, asynchronous job polling, rate limits, or other side effects beyond creating a new job.

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 a single, focused sentence with no filler. It front-loads the core action and key constraint, making it easy to parse quickly.

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

Completeness3/5

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

The schema and annotations cover the parameter and safety landscape, and the description gives the essential purpose. However, it omits lifecycle context such as how to retrieve the resulting job or whether it is asynchronous, which would be useful given the job-based nature of the tool.

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%, and each parameter has a clear one-line description. The tool description itself adds no additional meaning beyond what the input schema already provides, so the baseline score 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 ('Create'), a distinct resource ('new private search job'), and a unique action ('by changing the brief or criteria of a completed job'). The explicit non-destructive outcome ('The original job stays unchanged') further disambiguates it from similar lead-search tools.

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

Usage Guidelines3/5

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

The description implies use when refining a completed lead search and clearly frames the action, but it does not explicitly name alternatives such as start_lead_search or retry_lead_search, nor does it provide direct 'when not to use' guidance. Context is present but not fully explicit.

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

research_businessesResearch businesses from a briefA

Read-only

Inspect

Use for a quick synchronous search when the user supplies one natural-language brief and can wait for results in the current tool call. For durable progress, retry, export, or large agent workflows, use start_lead_search instead.

ParametersJSON Schema

Name	Required	Description	Default
`brief`	Yes	Example: Independent veterinary clinics in Berlin with an active first-party website. Exclude directories and chains.
`limit`	No	Maximum businesses in this response page.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`offset`	No	Zero-based result offset for this response page.
`output`	No	Compact minimizes tokens. Full preserves every returned field.	compact
`geography`	No	Optional explicit geography. Use when the brief does not make location clear.
`includeDiagnostics`	No	Include source status and explained exclusions.

Output Schema

ParametersJSON Schema

Name	Required	Description
`limit`	Yes	Maximum prospects requested for this page.
`offset`	Yes	Zero-based offset of this page.
`hasMore`	Yes	Whether another result page is available.
`results`	Yes
`warnings`	Yes	Limitations the agent should retain with downstream data.
`requestId`	Yes	Request identifier for support and diagnostics.
`durationMs`	No
`nextOffset`	No	Offset for the next synchronous result page, or null when complete.
`diagnostics`	No	Source status and explained candidate exclusions.
`resultCount`	Yes	Total accepted prospects before response pagination.
`returnedCount`	Yes	Prospects returned in this response page.
`schemaVersion`	Yes	Version of the result contract.
`searchedSources`	Yes	Discovery and first-party source types consulted.
`remainingFreeSearches`	No

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the synchronous, quick nature and the contrast with the durable asynchronous sibling, which is valuable context beyond the annotations. It does not contradict annotations and provides the expected call-time behavior.

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 with zero waste. The primary use case is front-loaded in the first sentence, and the alternative is clearly stated in the second. It is concise, structured, and every word contributes to the agent's decision.

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?

Given the tool's complexity (7 parameters, 1 required) and the presence of a detailed input schema and output schema, the description is sufficient. It explains the synchronous nature and the routing to the async sibling. It does not cover pagination or output details, but those are already in the schema, and the description provides the key decision guidance for an agent.

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 coverage is 100% and all seven parameters have detailed descriptions (e.g., brief example, limit bounds, fields enum). The description does not add parameter-specific semantics but reinforces that the brief is a natural-language query. With full schema coverage, a baseline of 3 is appropriate; the description adds no extra meaning beyond the 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?

The description states a specific verb ('research') and resource ('businesses'), and immediately defines the scope: a quick synchronous search from a natural-language brief. It distinguishes itself from start_lead_search by naming the alternative, making it clear this tool is for immediate results in the current call. No ambiguity.

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?

The description explicitly says 'Use for a quick synchronous search when the user supplies one natural-language brief and can wait for results in the current tool call' and then explicitly routes other workflows ('durable progress, retry, export, or large agent workflows') to start_lead_search instead. This gives both when-to-use and when-not-to-use guidance with a named alternative.

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

retry_lead_searchRetry a stopped lead searchAInspect

Create a replacement job when a prior job failed or exceeded its execution window. The original job stays available for audit.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Failed or timed-out source job id.
`jobToken`	Yes	Private token belonging to the source job.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Stable job identifier. Use it with jobToken in every lifecycle call.
`status`	Yes	Current durable job state.
`cacheHit`	No
`jobToken`	No	Private bearer token required to read, refine, or export this job.
`retryUrl`	Yes	Authenticated REST URL for creating a replacement after retryable failure.
`cancelUrl`	Yes	Authenticated REST URL for canceling queued or running work.
`exportUrl`	Yes	Authenticated CSV export URL. Add format=json for JSON.
`statusUrl`	Yes	Authenticated REST URL for job status and result pages.
`resultCount`	No
`expiresInSeconds`	Yes	Seconds until the private job and token expire.

TDQS

A4.5/5.0

Behavior4/5

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

The description makes the mutation explicit ('Create a replacement job') and adds a side effect detail (original stays for audit). It does not mention idempotency or permissions, but the annotations already cover the read-only and destructiveness hints, and the description aligns with them.

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 two sentences, concise and to the point, with no unnecessary details or repetition. It is well-structured and front-loads the core purpose.

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?

The description is complete enough given the output schema exists and the parameters are well-described. It does not cover error cases or output details, but these are not required for a tool of this simplicity.

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?

Both parameters have descriptions in the schema that add meaning: 'id' is 'Failed or timed-out source job id' and 'jobToken' is 'Private token belonging to the source job'. This exceeds simple name-based inference.

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?

Description clearly states the action ('Create a replacement job') and the specific object ('replacement job'), and distinguishes it from siblings by noting the original job stays for audit. It is clear and specific.

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 when to use it ('when a prior job failed or exceeded its execution window'), providing a clear condition. It does not explicitly name alternatives, but the condition sufficiently guides usage.

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

sandbox_businessesTest the Crawdar contractA

Read-onlyIdempotent

Inspect

Return deterministic fictional businesses without consuming provider capacity. Use this to test schemas, clients, and agent loops.

ParametersJSON Schema

Name	Required	Description	Default
`target`	No	Fictional business type echoed into deterministic test results.
`geography`	No	Fictional location echoed into deterministic test results.

Output Schema

ParametersJSON Schema

Name	Required	Description
`limit`	Yes	Maximum prospects requested for this page.
`offset`	Yes	Zero-based offset of this page.
`hasMore`	Yes	Whether another result page is available.
`results`	Yes
`warnings`	Yes	Limitations the agent should retain with downstream data.
`requestId`	Yes	Request identifier for support and diagnostics.
`durationMs`	No
`nextOffset`	No	Offset for the next synchronous result page, or null when complete.
`diagnostics`	No	Source status and explained candidate exclusions.
`resultCount`	Yes	Total accepted prospects before response pagination.
`returnedCount`	Yes	Prospects returned in this response page.
`schemaVersion`	Yes	Version of the result contract.
`searchedSources`	Yes	Discovery and first-party source types consulted.
`remainingFreeSearches`	No

TDQS

A5/5.0

Behavior5/5

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

The description clearly indicates the tool returns fictional deterministic data and has no provider-side consumption, aligning with the readOnlyHint annotation. It also implies idempotency through 'deterministic' and is consistent with the destructiveHint false annotation. No behavioral contradictions are present.

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 tightly written in two sentences with no redundant wording. It front-loads the primary purpose and immediately follows with concrete usage guidance.

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 the annotations, input schema, output schema, and sibling tool context, the description covers all essential information an agent needs: purpose, behavior, parameters, and safe usage. There are no missing critical details.

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?

Both parameters are described with their meaning and role in generating deterministic test results. The schema coverage is 100%, and the description adds that values are 'echoed' into results, clarifying how the parameters affect output.

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 uses a specific verb ('Return') and clearly identifies the resource as deterministic fictional businesses. It also distinguishes this tool from production data tools by noting it does not consume provider capacity and is intended for testing schemas, clients, and agent loops.

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?

The description explicitly states when to use the tool: 'Use this to test schemas, clients, and agent loops.' This provides clear guidance on the intended scenario and helps differentiate it from the sibling search/research tools.

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

scan_review_pain_pointsFind recurring customer complaintsA

Read-only

Inspect

Scan a named business or discover up to three businesses for recent recurring complaints. Returns individually sourced reviews and possible technical solutions. Coverage is sampled; unavailable reviews never mean no problems. Five scans per day. Google reviews require a configured provider.

ParametersJSON Schema

Name	Required	Description	Default
`target`	No
`website`	No
`business`	No
`geography`	No
`reviewUrls`	No
`googlePlaceId`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	No
`status`	No
`reports`	No
`limitations`	No

TDQS

A3.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds critical behavior beyond them: coverage is sampled (unavailable reviews never mean no problems), a five-scans-per-day rate limit, and a dependency on a configured provider for Google reviews. These are non-obvious traits that materially affect invocation.

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 three tight sentences, front-loading the primary action and purpose. Each sentence earns its place: the core function, the sampling caveat, and the operational constraints (rate limit and provider requirement). No filler.

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

Completeness2/5

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

With six parameters, zero schema descriptions, and no explanation of which parameters map to 'named business' or 'discover up to three businesses,' the description is insufficient for correct invocation. The output schema exists, so return format isn't a gap, but input semantics are entirely unaddressed. The operational constraints are helpful but don't compensate for missing parameter guidance.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameter meanings. It does not mention any of the six parameters (target, website, business, geography, reviewUrls, googlePlaceId) or how they relate to the described behavior. An agent cannot determine what to provide.

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 a specific action (scan) and resource (a named business or discover up to three businesses) for a distinct purpose (recurring complaints). It differentiates from sibling tools by focusing on complaints and solutions, not leads or generic research.

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

Usage Guidelines3/5

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

The description implies usage for complaint analysis but doesn't explicitly contrast with alternatives like search_businesses or research_businesses. It provides caveats (coverage sampling, rate limit, provider dependency) that inform when it's applicable, but lacks explicit when-not guidance or alternative routing.

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

search_businessesSearch businesses with structured criteriaA

Read-only

Inspect

Use for a quick synchronous search when target, geography, and qualification fields are already structured. Use research_businesses for a plain-language brief, or start_lead_search for durable asynchronous work.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum businesses in this response page.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`offset`	No	Zero-based result offset for this response page.
`output`	No	Compact minimizes tokens. Full preserves every returned field.	compact
`target`	Yes	Business type or concise target.
`geography`	Yes	City, region, country, or Worldwide.
`qualifier`	No	Optional required signals and exclusions that can be checked in public evidence.
`includeDiagnostics`	No	Include source status and explained exclusions.

Output Schema

ParametersJSON Schema

Name	Required	Description
`limit`	Yes	Maximum prospects requested for this page.
`offset`	Yes	Zero-based offset of this page.
`hasMore`	Yes	Whether another result page is available.
`results`	Yes
`warnings`	Yes	Limitations the agent should retain with downstream data.
`requestId`	Yes	Request identifier for support and diagnostics.
`durationMs`	No
`nextOffset`	No	Offset for the next synchronous result page, or null when complete.
`diagnostics`	No	Source status and explained candidate exclusions.
`resultCount`	Yes	Total accepted prospects before response pagination.
`returnedCount`	Yes	Prospects returned in this response page.
`schemaVersion`	Yes	Version of the result contract.
`searchedSources`	Yes	Discovery and first-party source types consulted.
`remainingFreeSearches`	No

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds useful context by characterizing the call as quick and synchronous, and there is no contradiction with the annotations.

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 concise, front-loaded with the primary use case, and efficiently contrasts sibling tools without unnecessary detail.

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?

The description, combined with the parameter schema and annotations, provides enough context for invoking a synchronous search and interpreting paging-related outputs. It could mention return shape more explicitly, but the output enum and parameter descriptions cover the essentials.

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 descriptions cover 100% of parameters, so the baseline applies. The tool description does not add much beyond the schema, though it does reinforce that target, geography, and qualifier are the structured search fields.

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?

Description uses the specific verb 'search' and identifies the resource 'businesses.' It clearly distinguishes from siblings by noting the structured-criteria synchronous use case versus research_businesses for plain-language briefs and start_lead_search for durable async work.

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 states when to use the tool: quick synchronous search when target, geography, and qualification fields are already structured. It also names alternatives for different scenarios, leaving little ambiguity about selection.

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

start_lead_searchStart a durable lead searchAInspect

Use for the recommended durable asynchronous workflow. Creates a private queued search job and returns a job id plus jobToken for progress polling, cursor paging, refinement, retry, cancellation, and CSV or JSON export.

ParametersJSON Schema

Name	Required	Description
`brief`	No	Natural-language business, geography, required signals, and exclusions. Use this instead of separate target and geography.
`limit`	No	Maximum accepted prospects retained by the job.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`target`	No	Business type or concise ideal-customer target. Pair with geography when brief is omitted.
`geography`	No	City, region, country, or Worldwide. Required with target when brief is omitted.
`qualifier`	No	Publicly verifiable requirements and exclusions.
`idempotencyKey`	No	Stable key for safely retrying the same job creation request.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	Yes	Stable job identifier. Use it with jobToken in every lifecycle call.
`status`	Yes	Current durable job state.
`cacheHit`	No
`jobToken`	No	Private bearer token required to read, refine, or export this job.
`retryUrl`	Yes	Authenticated REST URL for creating a replacement after retryable failure.
`cancelUrl`	Yes	Authenticated REST URL for canceling queued or running work.
`exportUrl`	Yes	Authenticated CSV export URL. Add format=json for JSON.
`statusUrl`	Yes	Authenticated REST URL for job status and result pages.
`resultCount`	No
`expiresInSeconds`	Yes	Seconds until the private job and token expire.

TDQS

A4.2/5.0

Behavior4/5

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

Description discloses that it creates a job, is asynchronous and queued, and returns identifiers for subsequent operations; consistent with annotations (idempotentHint=false, readOnlyHint=false).

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, front-loaded with usage recommendation, then concise feature list; no redundancy.

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?

Provides purpose, async nature, return identifiers, and downstream capabilities; since output schema exists, no need to detail return fields.

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 already covers all parameters with descriptions; description adds high-level workflow context but does not detail parameter usage, so baseline 3.

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 'creates' and resource 'private queued search job', and positions it as the recommended durable asynchronous workflow, distinguishing it from synchronous siblings.

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?

Explicitly says 'Use for the recommended durable asynchronous workflow' and enumerates downstream capabilities (polling, paging, refinement, retry, cancellation, export), signaling when to choose this tool; however, it does not explicitly name sibling tools for contrast.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateSep 8, 2026
- Addedscan_review_pain_points

8 tool updatesAug 26, 2026

Changedcancel_lead_search2 fields changed
- addedInput schema / properties / id / description
```
Added value: +"Queued or running job id."
```
- addedInput schema / properties / jobToken / description
```
Added value: +"Private token belonging to the job."
```

Changedget_lead_search4 fields changed

addedInput schema / properties / id / description

Added value: +"Job id returned by start_lead_search, refine_lead_search, or retry_lead_search."

addedInput schema / properties / jobToken / description

Added value: +"Private token returned with the job. Do not log or share it."

addedInput schema / properties / limit / description

Added value: +"Maximum prospects in this result page."

addedInput schema / properties / view / description

Added value: +"Compact minimizes tokens. Full retains detailed evidence fields."

Changedrefine_lead_search15 fields changed

addedInput schema / properties / brief / description

Added value: +"Replacement natural-language brief for the new job."

addedInput schema / properties / fields / description

Added value: +"Business fields to retain. Website and source evidence remain available for verification."

addedInput schema / properties / geography / description

Added value: +"Replacement city, region, country, or Worldwide."

addedInput schema / properties / id / description

Added value: +"Completed source job id returned by an earlier durable search call."

addedInput schema / properties / jobToken / description

Added value: +"Private token belonging to the source job."

addedInput schema / properties / limit / description

Added value: +"Maximum prospects retained by the new job."

addedInput schema / properties / qualifier / description

Added value: +"Replacement public requirements and exclusions."

addedInput schema / properties / target / description

Added value: +"Replacement business target for the new job."

addedOutput schema / properties / cancelUrl / description

Added value: +"Authenticated REST URL for canceling queued or running work."

addedOutput schema / properties / expiresInSeconds / description

Added value: +"Seconds until the private job and token expire."

addedOutput schema / properties / exportUrl / description

Added value: +"Authenticated CSV export URL. Add format=json for JSON."

addedOutput schema / properties / id / description

Added value: +"Stable job identifier. Use it with jobToken in every lifecycle call."

addedOutput schema / properties / retryUrl / description

Added value: +"Authenticated REST URL for creating a replacement after retryable failure."

addedOutput schema / properties / status / description
```
Added value: +"Current durable job state."
```

addedOutput schema / properties / statusUrl / description

Added value: +"Authenticated REST URL for job status and result pages."

Changedresearch_businesses12 fields changed

addedInput schema / properties / fields / description

Added value: +"Business fields to retain. Website and source evidence remain available for verification."

addedOutput schema / properties / diagnostics / description

Added value: +"Source status and explained candidate exclusions."

addedOutput schema / properties / hasMore / description

Added value: +"Whether another result page is available."

addedOutput schema / properties / limit / description

Added value: +"Maximum prospects requested for this page."

addedOutput schema / properties / nextOffset / description

Added value: +"Offset for the next synchronous result page, or null when complete."

addedOutput schema / properties / offset / description
```
Added value: +"Zero-based offset of this page."
```

addedOutput schema / properties / requestId / description

Added value: +"Request identifier for support and diagnostics."

addedOutput schema / properties / resultCount / description

Added value: +"Total accepted prospects before response pagination."

addedOutput schema / properties / returnedCount / description
```
Added value: +"Prospects returned in this response page."
```
addedOutput schema / properties / schemaVersion / description
```
Added value: +"Version of the result contract."
```

addedOutput schema / properties / searchedSources / description

Added value: +"Discovery and first-party source types consulted."

addedOutput schema / properties / warnings / description

Added value: +"Limitations the agent should retain with downstream data."

Changedretry_lead_search9 fields changed

addedInput schema / properties / id / description

Added value: +"Failed or timed-out source job id."

addedInput schema / properties / jobToken / description

Added value: +"Private token belonging to the source job."

addedOutput schema / properties / cancelUrl / description

Added value: +"Authenticated REST URL for canceling queued or running work."

addedOutput schema / properties / expiresInSeconds / description

Added value: +"Seconds until the private job and token expire."

addedOutput schema / properties / exportUrl / description

Added value: +"Authenticated CSV export URL. Add format=json for JSON."

addedOutput schema / properties / id / description

Added value: +"Stable job identifier. Use it with jobToken in every lifecycle call."

addedOutput schema / properties / retryUrl / description

Added value: +"Authenticated REST URL for creating a replacement after retryable failure."

addedOutput schema / properties / status / description
```
Added value: +"Current durable job state."
```

addedOutput schema / properties / statusUrl / description

Added value: +"Authenticated REST URL for job status and result pages."

Changedsandbox_businesses13 fields changed

addedInput schema / properties / geography / description

Added value: +"Fictional location echoed into deterministic test results."

addedInput schema / properties / target / description

Added value: +"Fictional business type echoed into deterministic test results."

addedOutput schema / properties / diagnostics / description

Added value: +"Source status and explained candidate exclusions."

addedOutput schema / properties / hasMore / description

Added value: +"Whether another result page is available."

addedOutput schema / properties / limit / description

Added value: +"Maximum prospects requested for this page."

addedOutput schema / properties / nextOffset / description

Added value: +"Offset for the next synchronous result page, or null when complete."

addedOutput schema / properties / offset / description
```
Added value: +"Zero-based offset of this page."
```

addedOutput schema / properties / requestId / description

Added value: +"Request identifier for support and diagnostics."

addedOutput schema / properties / resultCount / description

Added value: +"Total accepted prospects before response pagination."

addedOutput schema / properties / returnedCount / description
```
Added value: +"Prospects returned in this response page."
```
addedOutput schema / properties / schemaVersion / description
```
Added value: +"Version of the result contract."
```

addedOutput schema / properties / searchedSources / description

Added value: +"Discovery and first-party source types consulted."

addedOutput schema / properties / warnings / description

Added value: +"Limitations the agent should retain with downstream data."

Changedsearch_businesses12 fields changed

addedInput schema / properties / fields / description

Added value: +"Business fields to retain. Website and source evidence remain available for verification."

addedOutput schema / properties / diagnostics / description

Added value: +"Source status and explained candidate exclusions."

addedOutput schema / properties / hasMore / description

Added value: +"Whether another result page is available."

addedOutput schema / properties / limit / description

Added value: +"Maximum prospects requested for this page."

addedOutput schema / properties / nextOffset / description

Added value: +"Offset for the next synchronous result page, or null when complete."

addedOutput schema / properties / offset / description
```
Added value: +"Zero-based offset of this page."
```

addedOutput schema / properties / requestId / description

Added value: +"Request identifier for support and diagnostics."

addedOutput schema / properties / resultCount / description

Added value: +"Total accepted prospects before response pagination."

addedOutput schema / properties / returnedCount / description
```
Added value: +"Prospects returned in this response page."
```
addedOutput schema / properties / schemaVersion / description
```
Added value: +"Version of the result contract."
```

addedOutput schema / properties / searchedSources / description

Added value: +"Discovery and first-party source types consulted."

addedOutput schema / properties / warnings / description

Added value: +"Limitations the agent should retain with downstream data."

Changedstart_lead_search13 fields changed

addedInput schema / properties / brief / description

Added value: +"Natural-language business, geography, required signals, and exclusions. Use this instead of separate target and geography."

addedInput schema / properties / fields / description

Added value: +"Business fields to retain. Website and source evidence remain available for verification."

addedInput schema / properties / geography / description

Added value: +"City, region, country, or Worldwide. Required with target when brief is omitted."

addedInput schema / properties / limit / description

Added value: +"Maximum accepted prospects retained by the job."

addedInput schema / properties / qualifier / description

Added value: +"Publicly verifiable requirements and exclusions."

addedInput schema / properties / target / description

Added value: +"Business type or concise ideal-customer target. Pair with geography when brief is omitted."

addedOutput schema / properties / cancelUrl / description

Added value: +"Authenticated REST URL for canceling queued or running work."

addedOutput schema / properties / expiresInSeconds / description

Added value: +"Seconds until the private job and token expire."

addedOutput schema / properties / exportUrl / description

Added value: +"Authenticated CSV export URL. Add format=json for JSON."

addedOutput schema / properties / id / description

Added value: +"Stable job identifier. Use it with jobToken in every lifecycle call."

addedOutput schema / properties / retryUrl / description

Added value: +"Authenticated REST URL for creating a replacement after retryable failure."

addedOutput schema / properties / status / description
```
Added value: +"Current durable job state."
```

addedOutput schema / properties / statusUrl / description

Added value: +"Authenticated REST URL for job status and result pages."

4 tool updatesAug 26, 2026

Changedget_lead_search5 fields changed

addedOutput schema / properties / results / items / properties / contactRoute
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

addedOutput schema / properties / results / items / properties / criteria

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / prospectStatus
```
Added value: +{
+  "enum": [
+    "qualified",
+    "possible"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / whyMatch

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "prospectStatus",
+  "whyMatch",
+  "criteria",
+  "contactRoute"
+]

Changedresearch_businesses5 fields changed

addedOutput schema / properties / results / items / properties / contactRoute
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

addedOutput schema / properties / results / items / properties / criteria

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / prospectStatus
```
Added value: +{
+  "enum": [
+    "qualified",
+    "possible"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / whyMatch

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "prospectStatus",
+  "whyMatch",
+  "criteria",
+  "contactRoute"
+]

Changedsandbox_businesses5 fields changed

addedOutput schema / properties / results / items / properties / contactRoute
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

addedOutput schema / properties / results / items / properties / criteria

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / prospectStatus
```
Added value: +{
+  "enum": [
+    "qualified",
+    "possible"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / whyMatch

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "prospectStatus",
+  "whyMatch",
+  "criteria",
+  "contactRoute"
+]

Changedsearch_businesses5 fields changed

addedOutput schema / properties / results / items / properties / contactRoute
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```

addedOutput schema / properties / results / items / properties / criteria

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / prospectStatus
```
Added value: +{
+  "enum": [
+    "qualified",
+    "possible"
+  ]
+}
```

addedOutput schema / properties / results / items / properties / whyMatch

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "prospectStatus",
+  "whyMatch",
+  "criteria",
+  "contactRoute"
+]

6 tool updatesAug 22, 2026

Addedcancel_lead_search

Changedget_lead_search2 fields changed

addedOutput schema / properties / progress

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

changedOutput schema / properties / status / enum

Previous value: -[
-  "queued",
-  "running",
-  "completed",
-  "failed"
-]New value: +[
+  "queued",
+  "running",
+  "completed",
+  "failed",
+  "canceled"
+]

Changedrefine_lead_search3 fields changed

addedOutput schema / properties / cancelUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "queued",
-  "running",
-  "completed",
-  "failed"
-]New value: +[
+  "queued",
+  "running",
+  "completed",
+  "failed",
+  "canceled"
+]

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "jobToken",
-  "statusUrl",
-  "exportUrl",
-  "retryUrl",
-  "expiresInSeconds"
-]New value: +[
+  "id",
+  "status",
+  "statusUrl",
+  "exportUrl",
+  "retryUrl",
+  "cancelUrl",
+  "expiresInSeconds"
+]

Changedretry_lead_search3 fields changed

addedOutput schema / properties / cancelUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "queued",
-  "running",
-  "completed",
-  "failed"
-]New value: +[
+  "queued",
+  "running",
+  "completed",
+  "failed",
+  "canceled"
+]

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "jobToken",
-  "statusUrl",
-  "exportUrl",
-  "retryUrl",
-  "expiresInSeconds"
-]New value: +[
+  "id",
+  "status",
+  "statusUrl",
+  "exportUrl",
+  "retryUrl",
+  "cancelUrl",
+  "expiresInSeconds"
+]

Addedsandbox_businesses

Changedstart_lead_search4 fields changed

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Stable key for safely retrying the same job creation request.",
+  "maxLength": 128,
+  "minLength": 8,
+  "type": "string"
+}

addedOutput schema / properties / cancelUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "queued",
-  "running",
-  "completed",
-  "failed"
-]New value: +[
+  "queued",
+  "running",
+  "completed",
+  "failed",
+  "canceled"
+]

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "jobToken",
-  "statusUrl",
-  "exportUrl",
-  "retryUrl",
-  "expiresInSeconds"
-]New value: +[
+  "id",
+  "status",
+  "statusUrl",
+  "exportUrl",
+  "retryUrl",
+  "cancelUrl",
+  "expiresInSeconds"
+]

3 tool updatesAug 21, 2026

Changedrefine_lead_search2 fields changed

addedOutput schema / properties / retryUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "jobToken",
-  "statusUrl",
-  "exportUrl",
-  "expiresInSeconds"
-]New value: +[
+  "id",
+  "status",
+  "jobToken",
+  "statusUrl",
+  "exportUrl",
+  "retryUrl",
+  "expiresInSeconds"
+]

Addedretry_lead_search

Changedstart_lead_search2 fields changed

addedOutput schema / properties / retryUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "status",
-  "jobToken",
-  "statusUrl",
-  "exportUrl",
-  "expiresInSeconds"
-]New value: +[
+  "id",
+  "status",
+  "jobToken",
+  "statusUrl",
+  "exportUrl",
+  "retryUrl",
+  "expiresInSeconds"
+]

6 tool updatesAug 21, 2026

Changedexplain_crawdar1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "guidance": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "interfaces": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "resultLanes": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "resultLanes",
+    "guidance",
+    "interfaces"
+  ],
+  "type": "object"
+}

Addedget_lead_search
Addedrefine_lead_search
Addedresearch_businesses

Changedsearch_businesses7 fields changed

addedInput schema / properties / includeDiagnostics

Added value: +{
+  "default": true,
+  "description": "Include source status and explained exclusions.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 10,
+  "description": "Maximum businesses in this response page.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based result offset for this response page.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / output

Added value: +{
+  "default": "compact",
+  "description": "Compact minimizes tokens. Full preserves every returned field.",
+  "enum": [
+    "compact",
+    "full"
+  ]
+}

changedInput schema / properties / qualifier / description

Previous value: -"Optional public-evidence requirements."New value: +"Optional required signals and exclusions that can be checked in public evidence."

changedInput schema / properties / target / description

Previous value: -"Business type or plain-language target."New value: +"Business type or concise target."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "diagnostics": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "durationMs": {
+      "type": "integer"
+    },
+    "hasMore": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "nextOffset": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "remainingFreeSearches": {
+      "type": "integer"
+    },
+    "requestId": {
+      "type": "string"
+    },
+    "resultCount": {
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "confidence": {
+            "type": "number"
+          },
+          "email": {
+            "type": "string"
+          },
+          "entityConfidence": {
+            "type": "number"
+          },
+          "evidence": {
+            "items": {
+              "additionalProperties": true,
+              "properties": {
+                "kind": {
+                  "type": "string"
+                },
+                "label": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "evidenceQuality": {
+            "enum": [
+              "strong",
+              "moderate",
+              "weak"
+            ]
+          },
+          "fitStatus": {
+            "enum": [
+              "verified",
+              "likely"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "qualificationChecks": {
+            "items": {
+              "additionalProperties": true,
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "qualificationConfidence": {
+            "type": "number"
+          },
+          "sourceUrls": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "website": {
+            "type": "string"
+          },
+          "websiteUrl": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returnedCount": {
+      "type": "integer"
+    },
+    "schemaVersion": {
+      "type": "string"
+    },
+    "searchedSources": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "requestId",
+    "resultCount",
+    "returnedCount",
+    "offset",
+    "limit",
+    "hasMore",
+    "results",
+    "searchedSources",
+    "warnings"
+  ],
+  "type": "object"
+}

Addedstart_lead_search

2 tool updatesAug 21, 2026
- First observedexplain_crawdar
- First observedsearch_businesses

Related MCP Connectors

Nimrod ResearchOAuth
ai.orchis
Web research for agents: quality-scored Google search, webpage extraction, and deep research.
Browser Automation Search Web Scraping
1256
Sofya A
co.sofya
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Search Browser Automation Web Scraping
42
Tru8 Evidence Research A
io.github.SamYatesSmith
Source-traced evidence research for AI agents. We organise the evidence; you decide.
Research & Data Search RAG Systems
31
Context Relay A
io.github.chughes113
Compact, citation-verifiable public web context for AI agents, paid per use with x402.
RAG Systems Web Scraping Browser Automation
21

Related MCP Servers

aether-developer
Finance Search RAG Systems
EvidInvest
A
license
Not graded
quality
B
maintenance
Enables agents to search SEC filings, earnings transcripts, and EU regulations with ready-to-cite evidence, including exact passages and source links.
Updated 9 days ago (2026-09-02 19:24 UTC)
Apache 2.0
INDUSS Research Intelligence
Finance Research & Data Legal & Compliance
viraj43
F
license
Not graded
quality
C
maintenance
Enables AI assistants to perform institutional-grade research by retrieving and validating company, financial, industry, news, litigation, and funding data, then generating cited reports in Markdown, HTML, or PDF.
Updated 3 days ago (2026-09-08 18:31 UTC)
-
MarketIntel MCP Server
Research & Data Search
alexlcortes
A
license
Not graded
quality
C
maintenance
Enables AI chat clients to perform market research and competitive intelligence by gathering company overviews, competitor lists, product portfolios, pricing snapshots, and recent news via live Tavily search.
Updated 17 days ago (2026-08-25 14:14 UTC)
MIT
LastSearch-AI
Browser Automation RAG Systems Search
LastSearch-HQ
A
license
A
quality
A
maintenance
Evidence-backed web research for AI agents. Real-time search with cited claims, confidence scores, and compare mode showing raw LLM hallucination vs evidence-backed answers.
Updated 4 days ago (2026-09-07 21:09 UTC)
5
20
Apache 2.0

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.

Resources

Need Help?