Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

redraft_output

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

A3.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=falsecars, but the description adds substantial behavioral detail: manual-only operation, refusal when placeholders/broken links exist, preservation of revision history, and the required 'act' scope and Founder tier. This goes well beyond the annotations and gives an agent a clear picture of exact behavior and side effects.

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?

The description is a compact cluster of sentences, each delivering essential information: action, manual/AI distinction, refusal conditions, revision history, and auth/price. It is front-loaded with the core action and avoids wasted words, though slightly dense compared to the tersest examples.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers many behavioral aspects, there is no output schema and no mention of what the tool returns on success or how to verify the replacement (e.g., updated output object, revision ID). The complex draft_fence parameter is also only documented in the schema description, not in the tool description, leaving a significant contextual gap for an agent deciding how to invoke the tool.

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%, covering all three parameters including the nested draft_fence. The description does not add additional parameter-level semantics beyond referring to the body replacement; it relies on the schema's parameter descriptions, which is sufficient per the high coverage baseline.

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?

The description clearly states the action ('Replace') and resource ('drafted marketing output's body') and specifies when it applies ('before it is shipped'). It does not explicitly name or distinguish itself from the sibling tool 'update_draft', but the 'Manual replacement only' line implies a contrast with AI-driven redrafts, making the purpose reasonably unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful context: this is for manual replacement of a draft before shippingalert, and it notes refusal conditions. However, it does not explicitly mention when to use this tool versus an alternative like update_draft or accept_move, nor does it state any exclusions or prerequisites beyond the tier/scope.

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