@crawlbrulee/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Get an async scrape job result

scrape_result

Fetch the result of a finished async scrape job: markdown, cleaned/raw HTML, links, images, screenshot, metadata, and usage. Check scrape_status first to confirm done and avoid pending errors.

Instructions

Fetch the extracted content of a completed async scrape job (the same result shape as the synchronous scrape tool: markdown, cleaned HTML, raw HTML, links, images, screenshot, page metadata in metadata, and response_meta.usage). Errors if the job is still pending/running — check scrape_status first (status done) before calling this. Screenshot URLs are signed download links.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Job identifier returned by the `scrape_async` tool

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The URL that was actually scraped, after any redirects, in normalized form — the base that links, images, and internal labels are computed against
`links`	No	Links found on the page
`images`	No	Inline images found on the page
`markdown`	No	Page content converted to clean Markdown
`metadata`	No	Extracted page metadata (title, OG tags, etc.)
`raw_html`	No	Raw, unprocessed HTML of the page
`warnings`	No	Non-error notices about the scrape. Truncation codes — `screenshot_truncated` (long page exceeded the scrolling-screenshot height cap), `links_truncated` / `inline_images_truncated` (page had more links/images than the per-page extraction caps), `raw_html_truncated` / `metadata_truncated` (rendered HTML exceeded the per-page size budget) — mean the field is present but capped. Unavailability codes — `links_unavailable` / `inline_images_unavailable` / `metadata_unavailable` — mean that optional field could not be extracted and was omitted (null/empty) while the rest of the scrape succeeded, so an empty field carrying one of these does NOT mean the page had none. Stable string codes — clients can switch on them. Warnings are stored with the result: async result fetches and cache hits carry them too, filtered to the fields the request asked for.
`screenshot`	No	Screenshot of the page, if requested
`cleaned_html`	No	Cleaned HTML of the main page content
`content_type`	No	Content-Type header returned by the server
`requested_url`	Yes	The URL you requested, echoed verbatim — before any redirects
`response_meta`	Yes	Request-level metadata. `response_meta.usage` reports credits charged, the billed engine, the resolved proxy tier, and any screenshot-slice add-on.
`unsupported_fields`	No	Extract fields that were requested but are not supported for this content type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers: it discloses the error-on-pending behavior, the required status precondition, that screenshot URLs are signed download links, and that the payload mirrors the sync `scrape` output. This goes well beyond the bare schema. Slight gap: no mention of rate limits or whether results are retrievable more than once, but the key operational behaviors are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses, purpose first, then error/precondition guidance, then the signed-link caveat. Dense but not padded; every sentence earns its place. Slightly long relative to the simplest tools, but the content justifies it given the cross-tool preconditions.

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?

Complete for a one-parameter result-fetching tool: purpose, return shape, failure conditions, and prerequisite workflow are all stated, and an output schema exists to document the return values. Little an agent needs to call it correctly is missing.

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%—`job_id` is described as the identifier returned by `scrape_async`—so the baseline of 3 applies. The description adds no further parameter-level detail, but none is needed since the schema already ties the parameter to its origin tool.

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?

States a specific verb and resource—'Fetch the extracted content of a completed async scrape job'—and explicitly contrasts the result shape with the synchronous `scrape` tool. The async-scope distinction clearly separates it from siblings `scrape_async` (submission) and `scrape` (sync execution) without needing to inspect either schema.

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?

Provides explicit when-to-use guidance: call only after the job is `done`, and names the prerequisite tool `scrape_status` to check first. Also states the exclusion condition—errors if the job is `pending`/`running`—and references `scrape_async`'s return of `job_id`. This routes the agent unambiguously against its siblings.

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

Deploy Server