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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedAug 26, 2026

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."

Changed3 schema fields changedAug 22, 2026

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"
+]

AddedAug 21, 2026

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.

All Crawdar Business Research 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?