Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

crawler_job_delete

DestructiveIdempotent

Cancel and permanently delete a running ScraperAPI crawl job using its job ID. Use this to stop a crawl you no longer need.

Instructions

Cancel and delete a ScraperAPI crawl job.

    Irreversibly cancels a running crawl job and removes it. Use this to stop a
    crawl you no longer need.

    When to use:
    - Stopping a running crawl you started and no longer want

    When NOT to use:
    - Pausing temporarily — this permanently cancels the job (there is no resume)

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

    Returns:
        str: JSON confirming the job was cancelled.

    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
Behavior5/5

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

Annotations already mark destructiveHint and idempotentHint as true. The description adds important context: 'Irreversibly cancels', 'removes it', and 'there is no resume', which goes beyond the annotations and informs the agent of the permanent nature of the action.

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 well-organized with clear sections (overview, when to use, when not to use, args, returns, raises). It is concise, with no unnecessary words, and every sentence serves a 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 tool's simplicity, the description covers the purpose, usage conditions, parameters, return type, and possible errors. With annotations and schema, it provides complete context for an agent to use the tool correctly.

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?

The only parameter, job_id, is described as 'the id returned by crawler_job_start', which adds meaning beyond the schema's description. The description also mentions it is required, and the parameter structure is clear.

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 cancels and deletes a ScraperAPI crawl job. It specifies the verb 'Cancel and delete' and the resource 'crawl job', and distinguishes it from sibling tools like crawler_job_start and crawler_job_status.

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?

The description explicitly includes 'When to use' and 'When NOT to use' sections, advising to use it for stopping a crawl and not to use it for pausing because the action is irreversible. This provides clear guidance on when to choose this tool over alternatives.

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