@jam-jam/convert-mcp

Get a conversion job status

jj_get_job

Fetch a conversion job's current phase, per-step progress, and completed artifacts by ID to monitor jobs after a conversion request stops waiting.

Instructions

Fetches the current state of a conversion job by id: phase (queued/running/done/failed/cancelled), per-step progress, and the list of artifacts once done. Use this to check on a job after jj_convert_file or jj_convert_text stopped waiting for it.

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": {
      "id": "<id>"
    },
    "name": "jj_get_job"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Job id returned by jj_convert_file or jj_convert_text (e.g. "jb_9f2a1c7e4b6d8801").

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the return content (phase enum values, per-step progress, artifacts once done), which is genuinely useful. It omits what an agent would want for a polling tool: whether to poll repeatedly, expected latency transitions, or how an unknown/expired job id is reported.

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 sentences with zero filler: the first front-loads what is returned, the second front-loads when to call it. No restating of the title or the schema.

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?

With no output schema and no annotations, the description does the necessary work by naming the phase states and the progress/artifact return shape, and it links the tool to its producing calls. Slightly short of complete because return structure and failure behavior for an invalid id remain unaddressed.

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 description coverage is 100% and the single id parameter is fully documented in the schema, including the jb_ format example and its origin. The description's "by id" adds essentially nothing beyond the schema, so the baseline applies.

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?

States a specific verb and resource ("fetches the current state of a conversion job by id") and enumerates the returned state field, so an agent knows exactly what it gets back. It does not differentiate itself from the many other per-feature get_job siblings (jj_ai_music_get_job, jj_mastering_get_job, etc.), leaving the scope to be inferred from the name and the convert-tool references.

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?

Gives clear when-to-use guidance: check on a job after jj_convert_file or jj_convert_text stopped waiting for it, which ties the tool to a concrete workflow trigger. There is no explicit when-not or statement that other job families use their own get_job tool, but the conversion framing implicitly scopes it.

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