Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

apk_teardown_job_status

Poll an APK teardown job by job_id to get its current status (queued, processing, done, failed, lost) and retrieve the full result once processing completes.

Instructions

Poll an apk-teardown job's status/result. Returns the current status (queued, processing, done, failed, or lost) of a submitted job, and its full result once done.

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": "apk_teardown_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID from data.job_id returned by POST /apk-teardown/jobs; the response also supplies poll_path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.16
    • changedInput schema / properties / job_id / description
      Previous value: -"Job ID returned by Submit"New value: +"Job ID from data.job_id returned by POST /apk-teardown/jobs; the response also supplies poll_path"
  2. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the meaningful behavioral traits: the complete status enum, including 'lost' as a failure mode, and the fact that the full result is only available once done. The act of 'polling' also implies a safe repeated read. It stops short of stating whether calls are rate-limited or whether a 'lost' job can be recovered.

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?

Two tight sentences with zero waste. The action and scope lead, and the return-value explanation follows. Every clause earns its place.

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?

For a single-parameter, no-output-schema, no-annotation tool, the description covers what an agent needs: it explains the returned status set and that the result payload appears on completion. A brief note on polling cadence or terminal-state handling would close the last gap.

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% and the job_id schema description already explains its provenance (data.job_id from POST /apk-teardown/jobs, plus poll_path). The tool description only says 'of a submitted job', adding essentially nothing beyond what the schema documents. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb ('Poll') and resource ('apk-teardown job'), then enumerates the exact status values returned (queued, processing, done, failed, lost), making the tool's function and output shape unmistakable. An agent can tell this apart from apk_teardown_submit (which creates the job) and apk_teardown_delete_job without opening a schema.

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

Usage Guidelines3/5

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

The phrase 'of a submitted job' implies the tool is used after job creation, which is meaningful context. But there is no explicit guidance on when to poll, how often, when to stop (terminal states done/failed/lost are listed but not framed as stopping conditions), or which sibling to prefer for related tasks like diffs or timelines. Usage is implied rather than prescribed.

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

Deploy Server

Other Tools