Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Get run results

get_run_results
Read-only

Retrieve the status and result rows of a scraper run by runId, and page through large outputs with limit and offset.

Instructions

Get the status and result rows of a run started by one of the other tools. Use it for runs that were still running, or to page through large results.

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": {
      "runId": "<runId>"
    },
    "name": "get_run_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 50).
runIdYesThe runId returned by a scraper tool.
offsetNoRows to skip (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that this is a polling/retrieval step for in-flight runs and that results are pageable, which is useful beyond the annotations, but it says nothing about how long run results are retained, rate limits, or what statuses can appear.

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 with no filler; the core purpose is front-loaded and the usage hint follows immediately. Nothing could be removed without losing information.

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?

For a read-only polling tool with no output schema, the description should say more about what comes back (status values, whether paging metadata such as total counts is included). 'Status and result rows' hints at the shape but leaves an agent guessing about the response fields it will need to branch on.

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%: runId, limit (default 50, max 1000) and offset are fully documented in the schema. The description only implies that limit/offset are for paging and adds no format or syntax detail the schema lacks, so baseline 3 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?

The description names a specific verb and resource ('get the status and result rows of a run') and ties the resource to runs 'started by one of the other tools', which cleanly separates it from the scraper siblings that create the runs. An agent can tell this is the retrieval/polling counterpart without opening the schema.

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?

It gives two concrete usage triggers: runs that 'were still running' (polling after async start) and paging through large result sets. It stops short of naming an alternative tool or stating exclusions, but the when-to-use context is clear enough to act on.

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