ShapelessAI

Reply to a job

jobs_continue

Send another message to a job, optionally with files attached - also the way to resume a stuck or failed run with full history. Needs the write scope.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The job id.
`text`	Yes	The message, up to 4000 characters.
`model`	No	Brain for this run: claude-opus-5-5, claude-opus-5, claude-sonnet-5, claude-fable-5-1, gpt-5.6-sol or gpt-6-astra. Absent means the account's default. A model test runs the same goal once per model.
`autoRun`	No	Execute the plan the moment it is ready instead of pausing for approval. Deliverables still land as proposed drafts.
`budgetUsd`	No	Budget for this turn, in dollars.
`mediaKeys`	No	Media keys already in the account (from assets_upload or assets_list) to attach.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status"
+  ],
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuinely useful context beyond them: it requires the write scope (auth prerequisite) and that resuming carries full history. It stops short of saying whether the message re-triggers execution or what the budget/pause interactions are.

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, no filler, with the core action front-loaded and the resume use case plus the auth requirement trailing. Every clause carries information an agent needs.

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 an output schema present, return values need not be described, and the write scope, resume semantics and attachment capability are stated. Minor gaps remain around side effects of continuing a run (whether it consumes budget or resets state), but the definition is sufficient for correct invocation.

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%, so every parameter (id, text, model, autoRun, budgetUsd, mediaKeys) is already documented in the schema, including the 4000-char limit and model list. The description only alludes to 'files attached' (mediaKeys) and adds nothing further, so the baseline 3 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 ('Send another message to a job') and adds a second distinct purpose ('resume a stuck or failed run with full history'), which an agent could not infer from the name alone. It does not name the sibling it is not (jobs_run / jobs_create), so it falls short of the 5-level sibling differentiation.

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 a clear usage condition: this is the tool for resuming a stuck or failed run with full history preserved. However, it never contrasts with jobs_run (start a fresh run) or jobs_create, and states no when-not-to-use or prerequisite checks beyond the write scope.

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

All ShapelessAI 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.