Skip to main content
Glama
eliottreich

Crawdar Business Research

Start a durable lead search

start_lead_search

Launch an asynchronous lead-search job that compiles business prospects and returns a job ID for progress tracking, paging, refinement, retry, and CSV or JSON export.

Instructions

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
NameRequiredDescriptionDefault
briefNoNatural-language business, geography, required signals, and exclusions. Use this instead of separate target and geography.
limitNoMaximum accepted prospects retained by the job.
fieldsNoBusiness fields to retain. Website and source evidence remain available for verification.
targetNoBusiness type or concise ideal-customer target. Pair with geography when brief is omitted.
geographyNoCity, region, country, or Worldwide. Required with target when brief is omitted.
qualifierNoPublicly verifiable requirements and exclusions.
idempotencyKeyNoStable key for safely retrying the same job creation request.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStable job identifier. Use it with jobToken in every lifecycle call.
statusYesCurrent durable job state.
cacheHitNo
jobTokenNoPrivate bearer token required to read, refine, or export this job.
retryUrlYesAuthenticated REST URL for creating a replacement after retryable failure.
cancelUrlYesAuthenticated REST URL for canceling queued or running work.
exportUrlYesAuthenticated CSV export URL. Add format=json for JSON.
statusUrlYesAuthenticated REST URL for job status and result pages.
resultCountNo
expiresInSecondsYesSeconds until the private job and token expire.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

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.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliottreich/crawdar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server