Skip to main content
Glama
AceDataCloud

mcp-webextrator

by AceDataCloud

webextrator_get_task

Retrieve the result of an asynchronous extract or render task by providing its task ID or trace ID.

Instructions

Retrieve the result of a single previously created extract or render task.

Use this when:
- You submitted an async extract or render request with a callback_url
- You want to poll for the result of a specific task by its ID

Returns:
    JSON response containing the task status and result data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idNoTask UUID to retrieve. Use this to get the result of a single extract or render task.
trace_idNoTrace UUID as an alternative lookup for a single task. Use either task_id or trace_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains it is for retrieval (read-like), mentions async context, and notes the return type (JSON with status and result). Could add more on error handling or rate limits, but adequate given simplicity.

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 very concise with three clear sections: what it does, when to use, and what it returns. No wasted words.

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 retrieval tool with full schema coverage and an output schema, the description covers all necessary aspects: purpose, usage, and return format.

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%, so baseline is 3. The description adds value by explaining the purpose of task_id and trace_id, and how they are alternatives for lookup, exceeding the schema's minimal descriptions.

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 retrieves a result of a single previously created extract or render task. It uses a specific verb ('retrieve') and resource, and distinguishes it from siblings like webextrator_get_tasks_batch.

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 explicit use cases for async requests with callback_url and polling by task ID. It implies when to use this tool versus alternatives but does not explicitly exclude other scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/WebExtratorMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server