Skip to main content
Glama

Get task result (single poll)

get_task_result

Retrieve a CAPTCHA task's result in a single poll, returning status (processing/ready) and solution. Use for manual polling to extract the solved token for injection.

Instructions

Fetch a task result ONCE (a single poll).

Prefer get_task_result_wait, which polls for you. Use this only if you want to drive the poll loop yourself.

Returns a dict:

  • while solving: {"status": "processing", ...} — retry after 2-3 s. Poll no faster than once per 2 s (max 120 polls per task), and fetch the result promptly: the task is stored for only ~5 min before it expires with ERROR_NO_SUCH_CAPCHA_ID.

  • when ready: {"status": "ready", "solution": {...}, "cost": ..., ...}

The solution object is CapMonster's raw solution, returned verbatim — its shape differs per captcha type. Extract fields by the shape documented for that type (get_docs), e.g. gRecaptchaResponse/token for reCAPTCHA/Turnstile, nested domains[host].cookies.* for DataDome/Imperva, data.randstr + data.ticket for TenDI, etc.

IMPORTANT: several types return a userAgent (or headers["User-Agent"]) inside the solution — the solved token is bound to it, so reuse that exact UA in the browser / subsequent requests when injecting (Cloudflare Challenge, FunCaptcha, AWS WAF, Binance, TenDI, Basilisk).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.11

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does so thoroughly: it explains the processing vs ready statuses, retry timing, rate limits, 5-minute expiry, ERROR_NO_SUCH_CAPCHA_ID, raw solution shape, and userAgent binding. This far exceeds what a typical description provides.

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 long but every section earns its place: usage guidance, status returns, rate limits, expiry, solution shape, and UA binding are all relevant. It is front-loaded with the single-poll distinction and structured with bullets for easy scanning.

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?

Despite having no output schema and no annotations, the description gives a complete picture: return values, polling cadence, storage lifetime, error behavior, solution extraction pointers, and UA reuse instructions. An agent has enough context to call the tool correctly and interpret its result.

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

Parameters2/5

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

The schema has 0% description coverage, so the description must compensate for the task_id parameter, but it never mentions task_id, where it comes from, or its format. The parameter name is self-explanatory, but the description adds no semantic value beyond the schema.

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 opens with a specific verb and resource: 'Fetch a task result ONCE (a single poll).' It clearly distinguishes itself from the sibling get_task_result_wait by emphasizing single-poll behavior, leaving no ambiguity about what the tool does.

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?

It explicitly says to prefer get_task_result_wait and to use this tool only when driving the poll loop manually. This direct alternative guidance removes any guesswork about when to choose this tool over its siblings.

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