AfterLaunch

Correct a recorded publication

correct_move_publication

Destructive

Apply your user's explicit decision that a growth move's recorded publication is wrong: the shipped move is archived, its completion history is kept and no paid follow-through restarts. Pass the exact current job and attempt; legacy work also needs the exact move and legacy job states and updated_at. This never publishes anything. Free; requires the 'act' scope.

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": {
      "move_id": "<move_id>",
      "job_id": "<job_id>",
      "expected_attempt_id": "<expected_attempt_id>"
    },
    "name": "correct_move_publication"
  }
}

Input Schema

Name	Required	Description
`note`	No
`job_id`	Yes
`move_id`	Yes
`expected_attempt_id`	Yes	Exact current attempt; null for legacy work.
`expected_move_state`	No
`expected_legacy_state`	No	get_move: prepared_result.legacy_state ?? state.
`expected_move_updated_at`	No
`expected_legacy_updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the destructive=true annotation by specifying exactly what happens (shipped move archived, completion history kept, no follow-through restart), the cost ('Free'), and the required auth ('act' scope). This is rich behavioral context an agent needs before a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences that are front-loaded with the core action and its consequences, then the parameter guidance, then cost/scope. Every clause carries meaning, though the middle sentence is packed.

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?

For a destructive tool with 8 params (3 required), legacy branching, and no output schema, it covers effects, prerequisites, and the legacy-vs-current distinction well. It omits mismatch/error behavior and the response shape, leaving minor gaps.

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 description coverage is only 25%, so the description must compensate. It explains the current vs legacy branching ('Pass the exact current job and attempt; legacy work also needs the exact move and legacy job states and updated_at'), clarifying the otherwise-cryptic expected_* concurrency parameters; only the note and move_id meaning are left implicit.

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+resource ('correct a growth move's recorded publication') and the concrete effect (shipped move archived, completion history kept, no paid follow-through restarts), which distinguishes it from ship_move. It doesn't name sibling alternatives like undo_move or archive_move, so it is clear but not fully differentiated.

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 trigger condition: use when applying the user's explicit decision that the recorded publication is wrong, and clarifies it 'never publishes anything.' It stops short of naming when-not or alternative tools among the many siblings.

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

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

Resources

Need Help?