Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

report_job

Report a claimed attempt as running, ready_for_review or failed, always with its exact attempt_id. Ready needs prepared_content or a prepared asset_url and remains unpublished until the founder confirms. State shipped is retained only for stored legacy jobs whose attempt_id is null. Omitting an attempt never turns managed work into legacy work. Free; requires the 'act' scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes
job_idYesJob id (uuid), from list_queue.
asset_urlNoURL of the prepared asset. This does not claim publication.
attempt_idYesExact attempt id; null only when list_queue identified a legacy job.
fail_reasonNoRequired with 'failed': what stopped you.
receipt_urlNoA permalink to the proof.
session_urlNoYour own session URL, if you have one.
prepared_contentNoPrepared result body for ready_for_review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / asset_url / description
      Previous value: -"The live URL of what was published."New value: +"URL of the prepared asset. This does not claim publication."
    • addedInput schema / properties / attempt_id
      Added value: +{
+  "description": "Exact attempt id; null only when list_queue identified a legacy job.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / prepared_content
      Added value: +{
+  "description": "Prepared result body for ready_for_review.",
+  "maxLength": 20000,
+  "type": "string"
+}
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "running",
-  "shipped",
-  "failed"
-]New value: +[
+  "running",
+  "ready_for_review",
+  "shipped",
+  "failed"
+]
    • changedInput schema / required
      Previous value: -[
-  "job_id",
-  "state"
-]New value: +[
+  "job_id",
+  "attempt_id",
+  "state"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / session_url
      Added value: +{
+  "description": "Your own session URL, if you have one.",
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses meaningful side effects: ready remains unpublished until founder confirmation, shipped is retained only for stored legacy jobs, and omitted attempt_id cannot turn managed work into legacy. It also states the required scope and that the operation is free, which is useful behavioral context.

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?

Four dense sentences front-load the core action, and each subsequent sentence adds a distinct constraint or caveat. There is no filler, and the description stays compact despite covering several edge cases.

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?

For an action with 8 parameters, high schema coverage, and no output schema, the description covers the essential call logic: valid states, preconditions for ready, legacy handling, auth requirements, and cost. An agent can construct a correct call with minimal ambiguity.

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?

Schema coverage is high at 88%, so the baseline is 3. The description adds state-specific semantics such as ready requirements, the shipped legacy exception, and the exact attempt_id rule, going beyond what the property names alone convey. Some of this duplicates the schema's attempt_id description, but the added state logic earns a 4.

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 opens with a precise action: report a claimed attempt as running, ready_for_review, or failed, always with the exact attempt_id. It also clarifies the shipped edge case for legacy jobs, so the tool's scope is clear and distinguishable from generic state setters.

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 conditions: ready requires prepared_content or a prepared asset_url, shipped is only for legacy jobs with null attempt_id, and omitting attempt_id never converts managed work into legacy. It does not explicitly name sibling alternatives or say when not to use report_job, but the stated conditions strongly imply the decision context.

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

All AfterLaunch toolsInspect
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.

Resources