Skip to main content
Glama
ReftrixMCP
by TKMD

page.getJobStatus

Read-onlyIdempotent

Check the status, progress, and results of asynchronous page analysis jobs or batches, including failure details, so you can track completion and retrieve outcomes.

Instructions

Check the status of an async page analysis job or of a batch.

Pass exactly one of:

  • job_id: the job ID returned by page.analyze(async=true)

  • batch_id: the batch ID returned by page.batch_analyze

Returns for job_id:

  • Job state (waiting, active, completed, failed)

  • Progress percentage (0-100)

  • Result summary when completed

  • Error details when failed

Returns for batch_id:

  • Batch state (waiting, active, completed, failed, partial)

  • Progress percentage (0-100)

  • Summary (total, completed, failed, skipped counts)

  • Individual job results with states and webPageIds

Note: Requires Redis to be running. Jobs are retained for 24 hours after completion; batches for 48 hours.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "page.getJobStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoThe job ID returned by page.analyze(async=true). Do not combine with batch_id.
batch_idNoThe batch ID returned by page.batch_analyze. Do not combine with job_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / batch_id
      Added value: +{
      +  "description": "The batch ID returned by page.batch_analyze. Do not combine with job_id.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedInput schema / properties / job_id / description
      Previous value: -"The job ID returned by page.analyze(async=true)"New value: +"The job ID returned by page.analyze(async=true). Do not combine with batch_id."
    • removedInput schema / required
      Removed value: -[
      -  "job_id"
      -]
  2. Addedv0.1.8

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, the description discloses the Redis dependency, the 24-hour job and 48-hour batch retention windows, the full set of possible states for each path, and what each return shape contains. This is exactly the kind of operational context annotations cannot convey.

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 purpose is front-loaded in one line, then two clearly labeled blocks separate the job_id path from the batch_id path, each with a bulleted return summary. No sentence is redundant, and the mutual-exclusion constraint is stated before the return details.

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?

With no output schema, the description carries the return-value burden itself and does so thoroughly for both modes, including state enumerations and batch summary counts. The Redis prerequisite and retention limits round out everything an agent needs to call and interpret this tool correctly.

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 value by tying each parameter to the specific sibling tool that produces it and reiterating the mutual-exclusion rule. It stops short of explaining behavior for malformed or expired IDs, which would have pushed it higher.

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 first sentence names a specific verb ("Check the status") and two concrete resources ("async page analysis job" and "batch"), which cleanly separates it from page.analyze and page.batch_analyze, the tools that create those jobs. An agent can identify the tool's role without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes usage: pass exactly one of job_id (from page.analyze with async=true) or batch_id (from page.batch_analyze), which tells the agent where each ID originates and that they are mutually exclusive. It lacks an explicit "when not to use" statement or guidance on polling cadence, keeping it just below the top mark.

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