Crawdar Business Research

Refine a lead search

refine_lead_search

Creates a new private lead search from a completed one by replacing target, brief, geography, and fields while keeping the original job unchanged.

Instructions

Create a new private search job by changing the brief or criteria of a completed job. The original job stays unchanged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "jobToken": "<jobToken>"
    },
    "name": "refine_lead_search"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Completed source job id returned by an earlier durable search call.
`brief`	No	Replacement natural-language brief for the new job.
`limit`	No	Maximum prospects retained by the new job.
`fields`	No	Business fields to retain. Website and source evidence remain available for verification.
`target`	No	Replacement business target for the new job.
`jobToken`	Yes	Private token belonging to the source job.
`geography`	No	Replacement city, region, country, or Worldwide.
`qualifier`	No	Replacement public requirements and exclusions.

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

First observedv1.0.0Sep 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already indicate readOnly=false, destructive=false, and idempotent=false. The description adds that the original job remains unchanged, but it does not disclose persistence behavior, asynchronous job polling, rate limits, or other side effects beyond creating a new job.

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 a single, focused sentence with no filler. It front-loads the core action and key constraint, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema and annotations cover the parameter and safety landscape, and the description gives the essential purpose. However, it omits lifecycle context such as how to retrieve the resulting job or whether it is asynchronous, which would be useful given the job-based nature of the tool.

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%, and each parameter has a clear one-line description. The tool description itself adds no additional meaning beyond what the input schema already provides, so the baseline score applies.

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 ('Create'), a distinct resource ('new private search job'), and a unique action ('by changing the brief or criteria of a completed job'). The explicit non-destructive outcome ('The original job stays unchanged') further disambiguates it from similar lead-search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when refining a completed lead search and clearly frames the action, but it does not explicitly name alternatives such as start_lead_search or retry_lead_search, nor does it provide direct 'when not to use' guidance. Context is present but not fully explicit.

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

Deploy Server