Skip to main content
Glama

Start a search (spends credits)

run_search

Starts a ready search for leads leads. SPENDS CREDITS: first call quote_search, show the price to the user, and only after their explicit yes call this with confirm_credits = the quote's credits_high. stop_at_target (default true) stops at the number of leads. Returns at once (maybe queued); then poll get_search every 30-60 s. Needs a plan or credits on the balance. [REST: POST /api/tasks/{id}/run]

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": {
      "task_id": "<task_id>",
      "leads": "<leads>",
      "confirm_credits": "<confirm_credits>"
    },
    "name": "run_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadsYes
task_idYesThe search id (task id), e.g. from list_searches or create_search.
versionNoThe spec version from get_search (optional: protects against an edit made meanwhile in the web).
stop_at_targetNo
confirm_creditsYesThe price in credits the matching quote returned, shown to the user and confirmed by them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent); the description adds the behavior that actually matters — this operation spends credits, requires user confirmation, returns immediately and may be queued, and needs a funding precondition. That is substantially more than the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the credit warning and the required confirmation sequence, so the most consequential information arrives first. The prose is dense to the point of being run-on, and the trailing REST endpoint note is peripheral, but no sentence is wasted.

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?

For a credit-spending, non-idempotent action with no output schema, the description covers the confirmation gate, the return semantics (immediate, possibly queued), the polling follow-up, and the account requirement. An agent has everything needed to call it safely without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 60% schema coverage, the description usefully explains stop_at_target ('stops at the number of leads', default true) and ties confirm_credits to the quote's credits_high, which the schema does not state. It leaves leads and version to the schema, so it complements rather than fully documents the parameters.

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 and resource ('Starts a ready search for `leads` leads') and implicitly distinguishes itself from the read-only siblings it names (quote_search, get_search). An agent can tell this is the execution step versus the quoting and polling steps.

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

Usage Guidelines5/5

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

Gives an explicit ordered procedure: call quote_search first, show the price, get an explicit yes, then call this with confirm_credits equal to the quote's credits_high. It also specifies the follow-up (poll get_search every 30-60 s) and the precondition (a plan or credits on the balance).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources