Skip to main content
Glama
ClearStack Data MCP server

ClearStack Data MCP server

by Wordhalm

Get results of a running search

get_run_results
Read-onlyIdempotent

Wait for an unfinished Apify run and return its items at no extra cost, using the runId from a previous call that returned finished=false.

Instructions

When another tool returned finished=false, wait for that Apify run and return its items. No extra cost: the run is already paid for.

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
runIdYesrunId returned by a previous tool call.
maxItemsNoDefaults to the cap of the original call.

Output Schema

NameRequiredDescriptionDefault
actorYesApify Actor that produced the data
itemsYes
runIdYesApify run ID; pass it to get_run_results if finished is false
statusYesApify run status, e.g. SUCCEEDED or RUNNING
finishedYesfalse when the run was still going and items are partial
itemCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context — this call blocks/waits and incurs no additional cost because the run is already paid for — but says nothing about timeout, failure handling, or polling behavior, which is the main unknown for a wait-style tool.

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 tight sentences, with the precondition front-loaded before the behavioral note. Nothing is redundant and every clause carries information.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The gaps are behavioral edge cases (timeout, failed runs, whether it polls) rather than missing essentials for correct invocation.

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%, so both runId and maxItems (with its default and 1-2000 bounds) are already fully documented. The description only loosely gestures at runId ('that Apify run') and never mentions maxItems, so it adds little beyond the schema — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb pair ('wait for that Apify run and return its items') and names the exact signal that identifies the target run ('finished=false'). It is unambiguous about what the tool returns, though it does not explicitly contrast itself with the sibling 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 Guidelines4/5

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

It gives a precise triggering condition: use this only after another tool returned finished=false. That is far better than implied usage, but it does not cover edge cases such as what to do if the run never completes or fails, and it names no alternative retrieval path.

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