web-data-mcp

by fctpe

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get actor run status

get_run_status

Read-onlyIdempotent

Check whether an actor run has completed and find where its dataset lives. Poll as often as needed.

Instructions

Check whether an actor run has finished and where its dataset is. Free and safe to poll.

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_run_status"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes	Run id returned by run_actor or scrape_url

Output Schema

Name	Required	Description	Default
`run_id`	Yes
`status`	Yes
`finished`	Yes
`dataset_id`	Yes
`started_at`	Yes
`finished_at`	Yes
`status_message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds value by specifying 'Free and safe to poll' and disclosing that the response includes dataset location. This goes beyond the structured annotations without contradicting them.

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 two short sentences, front-loaded with the core purpose, and contains no filler. Every word contributes to understanding the tool's function and safety.

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 simple status-checking tool with one parameter, rich annotations, and an output schema, the description is complete. It states what the tool does, what information it provides, and that it is safe to poll, fully covering the essential context.

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?

The schema already provides 100% coverage for the single parameter (run_id) with a helpful description. The tool description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 clearly states the tool's function: 'Check whether an actor run has finished and where its dataset is.' This is a specific verb+resource statement that distinguishes it from siblings like run_actor or fetch_dataset_items, which handle running or retrieving data.

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?

The description provides clear context: it is for checking run completion and locating the dataset, implying use after triggering a run. It also notes it is 'free and safe to poll,' indicating suitability for repeated use. However, it does not explicitly mention when not to use it or name alternative tools for other purposes.

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

Deploy Server