qencode

wait_for_job

Read-onlyIdempotent

Deprecated: does not wait. Use list_jobs to watch a job.

Hosts abort long tool calls (~60s), so this tool cannot poll an
encode. Call `list_jobs` with this `task_token` — the jobs card
refreshes itself while the job is in flight. For one snapshot use
`get_job_status`. For output artefacts after the job finishes use
`get_job_status_detailed`. Do not loop status yourself and do not
resubmit.

`timeout_seconds` and `poll_interval` are ignored; they remain so
old clients can still call this tool without a schema error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task_token`	Yes
`poll_interval`	No
`timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`use`	Yes
`deprecated`	Yes
`task_token`	Yes
`instructions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 8, 2026

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedOutput schema / properties / api_version

Removed value: -{
-  "type": [
-    "string",
-    "integer",
-    "number"
-  ]
-}

removedOutput schema / properties / audios
```
Removed value: -{
-  "type": "array"
-}
```
addedOutput schema / properties / deprecated
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / duration

Removed value: -{
-  "type": [
-    "number",
-    "integer",
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / error

Removed value: -{
-  "type": "integer"
-}

removedOutput schema / properties / error_description

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / images
```
Removed value: -{
-  "type": "array"
-}
```
addedOutput schema / properties / instructions
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / percent

Removed value: -{
-  "type": [
-    "integer",
-    "number",
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / source_size

Removed value: -{
-  "type": [
-    "integer",
-    "number",
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / status_url

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / task_token
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / texts
```
Removed value: -{
-  "type": "array"
-}
```
addedOutput schema / properties / use
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / videos
```
Removed value: -{
-  "type": "array"
-}
```
removedOutput schema / properties / warnings
```
Removed value: -{
-  "type": "array"
-}
```

addedOutput schema / required

Added value: +[
+  "deprecated",
+  "task_token",
+  "use",
+  "instructions"
+]

First observedAug 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that timeout_seconds and poll_interval are ignored, explains why they remain for backward compatibility, and reveals the host's ~60s abort limit. It also states that the tool does not block or poll, which is critical behavior beyond the annotations.

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 description is dense but every sentence carries weight: deprecation status, alternative tools, host constraints, and parameter handling. The most important fact ('does not wait') is front-loaded, and warnings are grouped logically without redundancy.

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?

Given that this is a deprecated compatibility stub with an output schema, the description says everything an agent needs: why the tool exists, what it does not do, which alternatives to use, and how to treat its parameters. Nothing essential is missing.

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?

With 0% schema description coverage, the description compensates by explicitly stating that timeout_seconds and poll_interval are ignored and explaining their compatibility purpose. It also references task_token in context with list_jobs, though it does not elaborate on token format or validation, leaving minor room for interpretation.

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 upfront that the tool is deprecated and does not wait, making its current no-op compatibility role unmistakable. It also names the sibling tools that should be used instead, which clearly distinguishes it from list_jobs, get_job_status, and get_job_status_detailed.

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?

The description gives explicit routing guidance: use list_jobs to watch a job, get_job_status for a single snapshot, and get_job_status_detailed for output artifacts. It also warns against looping status checks and resubmitting, leaving no ambiguity about when and how this tool should be bypassed.

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

All qencode tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.