Skip to main content
Glama

SteadyScrape Local Leads

Get results of a longer run

get_results
Read-onlyIdempotent

Fetch the results of a find_local_businesses, business_reviews or review_summary call that returned a run_id because it took longer than about two minutes. Returns the status while it is still running. Free: the original run is billed.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id from the earlier call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real value beyond the annotations: it discloses polling semantics ('returns the status while it is still running') and billing behavior ('Free: the original run is billed'), which annotations cannot express. It does not say whether the caller should retry, how often, or how completion is signaled, leaving a gap for a long-running-retrieval tool.

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?

Three short sentences with the precondition and behavior front-loaded; nothing is padded. The 'Free: the original run is billed' sentence is compressed to the point of slight ambiguity about exactly what is free, costing a point.

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?

With no output schema, the description should carry more of the return contract for a polling tool: what the final payload contains and how completion is indicated. It covers the still-running case and cost, but stops short of describing the completed result, so an agent must discover that at call time.

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?

Schema coverage is 100% with a single parameter, so the schema already carries the baseline. The description does add meaning by specifying which upstream tools' run_ids are valid inputs, which the schema's terse 'from the earlier call' does not.

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?

Specific verb (fetch) plus resource (results) plus the exact originating calls (find_local_businesses, business_reviews, review_summary) whose run_id qualifies. An agent can immediately distinguish this from the three sibling tools that start the runs.

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?

States the trigger condition clearly: use this only after one of the named calls returned a run_id because it exceeded roughly two minutes. The exclusions are implicit rather than stated (e.g. don't poll without a run_id), but the routing rule is unambiguous.

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