Skip to main content
Glama
MCP Design System Extractor

MCP Design System Extractor

job_status

Check async job status and progress, then retrieve the completed result. Poll after get_component_html to get your extracted component HTML without blocking.

Instructions

Check the status of an async job. Returns status, progress, and result when completed. Poll this endpoint to get results from get_component_html.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job ID returned from get_component_html

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the job failed
job_idYes
resultNoPresent once the job completes
statusYes
created_atYes
started_atNo
completed_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose that this is an async, poll-driven operation returning status, progress, and a result on completion. It omits important behavior: what terminal/failure states look like, whether the result disappears after retrieval, and any guidance on polling frequency or expiry.

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?

Three short sentences, front-loaded with the core purpose, then return values, then the usage link to the producing tool. No filler and nothing buried.

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?

An output schema exists, so return values need not be restated, and the description supplies the async-polling framing an agent needs to call it correctly. The remaining gap is around failure/completion state handling rather than the call itself.

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 single job_id parameter is already documented as coming from get_component_html, which the description merely echoes. No additional meaning (format, whether IDs expire, behavior on unknown IDs) is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Check the status of an async job') and immediately enumerates what is returned (status, progress, result when completed). It clearly reads as a polling endpoint, but it never distinguishes itself from the sibling tools job_list and job_cancel, so an agent must infer the boundary.

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 gives concrete usage direction: 'Poll this endpoint to get results from get_component_html,' which ties the tool to its producing sibling and explains the polling workflow. It stops short of stating when NOT to use it (e.g., use job_cancel to abort, job_list to enumerate jobs) or how often to poll.

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