Crawdar Business Research

Start a durable lead search

start_lead_search

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.

Input Schema

TableJSON 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

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.

Changed13 schema fields changedAug 26, 2026

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

Changed4 schema fields changedAug 22, 2026

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

Changed2 schema fields changedAug 21, 2026

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

AddedAug 21, 2026

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.

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?