Crawdar Business Research

Get a lead search page

get_lead_search

Read-onlyIdempotent

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

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 26, 2026

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

Changed5 schema fields changedAug 26, 2026

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

Changed2 schema fields changedAug 22, 2026

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

AddedAug 21, 2026

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.

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?