alterlab-mcp-server

Get Job

alterlab_get_job

Read-onlyIdempotent

Fetches the status and result of an asynchronous scrape job by job_id, so you can poll long-running scrapes or screenshots without re-running the billed request.

Instructions

Fetch the status and result of an asynchronous scrape job by job_id. Use this when alterlab_scrape or alterlab_screenshot returns a job_id instead of content (a long-running scrape that outlived the synchronous wait window). Status values: queued, processing, succeeded, failed, rejected (rejected = not processed due to insufficient balance; stop polling and check the balance). Polling is free; do not re-run the scrape, which would be billed again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "alterlab_get_job"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID returned by an async or downgraded scrape (alterlab_scrape reports it when a scrape outlives the ~85s synchronous window)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.9.0Oct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly and idempotent, and the description goes further with behavioral facts the annotations cannot express: the full status vocabulary (queued/processing/succeeded/failed/rejected), the billing consequence of 'rejected', and that polling is free while re-scraping is billed again.

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?

Front-loaded with the core action, followed by when-to-use, status semantics, and the cost caveat. Every sentence carries operational weight; the parenthetical on 'rejected' is slightly dense but justified by the polling advice.

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?

Single-parameter read tool with full annotation and schema coverage and no output schema; the description supplies everything else an agent needs — the polling workflow, terminal states, and the cost/side-effect warning about re-running the scrape.

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 already 100%, so the baseline is 3, but the description adds the origin semantics of job_id — that it comes from a scrape that outlived the synchronous wait window — which tells the agent where to obtain a valid value rather than just its type.

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 status and result of an asynchronous scrape job') and scopes it by job_id, which distinguishes it cleanly from siblings like alterlab_scrape, alterlab_batch_status and alterlab_crawl_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?

Explicitly names the trigger condition: use this when alterlab_scrape or alterlab_screenshot returns a job_id instead of content. It also gives a clear stop condition (rejected = insufficient balance, stop polling) and an explicit anti-pattern (do not re-run the scrape).

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