Skip to main content
Glama
massanaRoger

extracto-mcp

by massanaRoger

Submit an async extraction job

extract_async
Read-only

Submit an asynchronous extraction job for heavy, slow, or anti-bot-protected pages. Returns a job ID immediately for polling until success or failure.

Instructions

Submit an asynchronous extraction job for a heavy, slow, or anti-bot-protected page. Returns a job id immediately; poll it with get_job until status is "success" or "failed". Use this instead of extract when a page is large or likely to need stealth rendering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe public HTTPS URL to extract from.
schemaYesAn object mapping each field name to a type. A type is one of the literals "string", "number", "boolean", "array", "object"; OR a one-element array for a list (e.g. ["string"] for a list of strings, or [{ "title": "string", "price": "number" }] for a list of objects); OR a nested object (e.g. { "author": { "name": "string" } }). Use the most specific shape you can. Example: { "title": "string", "price": "number", "tags": ["string"], "reviews": [{ "user": "string", "stars": "number" }] }.
examplesNoUp to 3 few-shot examples.
webhookUrlNoOptional URL to receive a signed callback when the job completes.
idempotencyKeyNoOptional key; a retry with the same key replays the original job.
Behavior4/5

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

The description adds async behavior and polling pattern beyond the annotations. Annotations declare readOnlyHint: true and openWorldHint: true, which are consistent. The description provides valuable behavioral context without contradiction.

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 sentences, front-loaded with purpose, immediately followed by usage guidance. No redundant or vague language.

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?

Captures the key aspects: async submission, polling flow, alternatives, and mentions status outcomes. Sufficient for an async job tool with sibling context and schema coverage.

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%, so baseline is 3. The description does not add extra meaning beyond what the schema provides, but it implies the 'url' and 'schema' are for extraction. Adequate.

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 action ('Submit') and resource ('asynchronous extraction job'), and specifies the context ('heavy, slow, or anti-bot-protected page'). It distinguishes from sibling tools by naming 'extract' as the alternative.

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?

Explicit guidance on when to use this tool (heavy/slow/anti-bot pages) and when to use alternatives (use 'extract' for simpler pages). Also explains polling flow with 'get_job'.

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/massanaRoger/extracto-mcp'

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