Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

crawler_job_status

Read-onlyIdempotent

Track the progress of a crawl job by retrieving counts of done, failed, and active pages. Use to detect completion after starting a job.

Instructions

Get the status of a ScraperAPI crawl job.

    Returns counts of pages that are done, failed, and active for the job,
    letting you track progress and detect completion. Poll this after
    'crawler_job_start' until the job is finished.

    When to use:
    - Tracking progress or detecting completion of a job from 'crawler_job_start'

    When NOT to use:
    - Retrieving the crawled page contents (those are delivered to the job's
      callback_url webhook, not returned here)

    Args:
        params (CrawlerJobRefParams): job_id (required) — the id returned by
            crawler_job_start.

    Returns:
        str: JSON with the job's page counts (done/failed/active).

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, no destructiveHint. The description adds concrete details: returns JSON with counts, raises ToolError for missing API key, rate limit, or request failure. Does not contradict annotations.

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?

Well-structured with clear sections (main, when to use, when not, args, returns, raises). Slightly verbose but all sentences add value. Front-loaded with purpose.

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?

Given the simple parameter set and rich annotations, the description covers return format, error conditions, relationship to other tools, and expected usage pattern. No gaps.

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

Parameters5/5

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

Only one parameter (params.job_id) whose description in the description reinforces the schema: 'job_id (required) — the id returned by crawler_job_start.' The schema itself has a description, but the description adds context by linking to the previous 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?

The description clearly states 'Get the status of a ScraperAPI crawl job' and specifies it returns counts of pages (done, failed, active). It distinguishes from siblings like crawler_job_start and crawler_job_delete by its polling purpose.

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 'When to use' and 'When NOT to use' sections: use for tracking progress/detecting completion, not for retrieving page contents (which go to callback_url). Mentions polling after crawler_job_start.

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/scraperapi/scraperapi-mcp'

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