Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Update output draft

redraft_output
Destructive

Replace a drafted marketing output's body before it is shipped. Manual replacement only: the AI redraft stays in the app. A draft carrying an unfilled placeholder or a broken link is refused, and the previous draft is kept as revision history. Free; requires the 'act' scope and Founder tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftYesThe replacement draft body, 1 to 20000 characters.
output_idYesOutput id (uuid), from list_outputs.
draft_fenceNoFor a content pilot edit, return draft_fence unchanged from get_move or get_output. Refresh after a conflict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / draft_fence
      Added value: +{
+  "additionalProperties": false,
+  "description": "For a content pilot edit, return draft_fence unchanged from get_move or get_output. Refresh after a conflict.",
+  "properties": {
+    "attempt_id": {
+      "format": "uuid",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "candidate_id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "draft": {
+      "maxLength": 20000,
+      "type": "string"
+    },
+    "job_id": {
+      "format": "uuid",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "job_updated_at": {
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "move_id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "move_state": {
+      "type": "string"
+    },
+    "move_updated_at": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "required": [
+    "move_id",
+    "move_state",
+    "move_updated_at",
+    "job_id",
+    "attempt_id",
+    "job_state",
+    "job_updated_at",
+    "candidate_id",
+    "draft"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / output_id / description
      Previous value: -"The drafted output id (uuid), from list_outputs."New value: +"Output id (uuid), from list_outputs."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which only give destructiveHint=true, readOnly=false, openWorld=false). It discloses validation behavior (unfilled placeholders and broken links are refused), reversibility (previous draft kept as revision history), cost (free), and authorization requirements ('act' scope, Founder tier). This is exactly the extra context an agent needs before mutating.

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?

Three sentences, front-loaded with the action and staged from purpose to constraints to cost/auth. Every sentence carries new information with no repetition.

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?

No output schema exists and this is a destructive mutation, yet the description covers validation rules, history retention, cost, and scope requirements. The only unaddressed area is the conflict/refresh flow, which is partially handled by the schema's draft_fence description.

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 all three parameters including the nested draft_fence object are already documented in the schema. The description adds no syntax, format, or constraint detail beyond that, 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?

Names a specific verb (replace) and resource (a drafted marketing output's body) with scope ('before it is shipped'). It differentiates behaviorally from the AI-redraft flow via 'Manual replacement only', but never names the obvious sibling update_draft, so routing still requires inference.

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?

'before it is shipped' and 'Manual replacement only: the AI redraft stays in the app' establish clear context and an implicit exclusion against the automated path. However, it does not explicitly name update_draft as the alternative or state when-not to use this tool.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources