Crawdar Business Research

Retry a stopped lead search

retry_lead_search

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

Input Schema

TableJSON 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

TableJSON 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.3/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the operation creates a new replacement job and that the original job is preserved for audit purposes. This adds meaningful non-destructive side-effect context, though it does not detail every consequence of non-idempotent calls.

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 the core action and trigger condition, with zero filler. The audit note is a single clause that earns its place.

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 two-parameter tool with a fully documented schema and an output schema, the description covers why to call it, what happens, and what is preserved. No critical information needed for correct invocation 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%: both id and jobToken are already explained in the input schema. The description adds no new parameter-level meaning, which is acceptable under the baseline for fully documented schemas.

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-resource pair ('Create a replacement job') and gives the exact trigger condition (failed or exceeded execution window). This clearly distinguishes the tool from siblings like start_lead_search or get_lead_search, while the title reinforces the retry action.

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 states a clear when-to-use condition: a prior job failed or exceeded its execution window. It does not explicitly name alternatives or when-not-to-use cases, so it stops short of a 5.

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

All Crawdar Business Research 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.4/5.0

Disambiguation4/5

Most tools map to distinct lifecycle actions (start/get/cancel/refine/retry), and the descriptions make those boundaries clear. The only real overlap is between research_businesses and search_businesses, which both perform synchronous lookups but are separated by natural-language vs structured input.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern, with lead_search reused across lifecycle operations. Even explain_crawdar and sandbox_businesses fit the naming convention well.

Tool Count5/5

Nine tools is well within the appropriate range for a business-research MCP server. The count balances synchronous search, a durable async job lifecycle, sandbox testing, and self-documentation without feeling bloated.

Completeness4/5

The async lead-search lifecycle is well covered with start, get, cancel, refine, and retry, and the synchronous and sandbox search tools cover adjacent needs. However, export is mentioned in start_lead_search but not exposed as a tool, and there is no way to list existing jobs, leaving minor gaps.

Resources

Need Help?