Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Update move draft

update_draft
Destructive

Replace a pending growth move's marketing draft body before shipping. A draft carrying an unfilled placeholder or a broken link is refused rather than saved. 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>",
      "draft_content": "<draft_content>"
    },
    "name": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
move_idYesMove id (uuid), from list_feed.
draft_fenceNoFor a content pilot edit, return draft_fence unchanged from get_move or get_output. Refresh after a conflict.
draft_contentYesThe replacement draft body, 1 to 20000 characters.

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 / move_id / description
      Previous value: -"The growth move id (uuid), from list_feed."New value: +"Move id (uuid), from list_feed."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds real behavioral context: invalid drafts with unfilled placeholders or broken links are refused rather than saved, and the call requires the 'act' scope and is free. It does not, however, explain what replacing does to the prior draft body or how conflicts surface.

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 short sentences, all front-loaded: the replacement action first, then the validation rule, then cost and scope. Every sentence carries distinct information with no redundancy.

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 no output schema and a nested draft_fence object, the description covers the mutation, its validation gate, and its auth/cost profile, and the schema carries the fence semantics. It is nearly complete, though it could say more about what happens on success (e.g. move state transition).

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 move_id, draft_content, and the nested draft_fence are already documented in-schema, including the conflict-refresh note on draft_fence. The description adds no parameter-level detail beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb and resource ('Replace a pending growth move's marketing draft body') and scopes it temporally ('before shipping'), which separates it from siblings like redraft_output or propose_move. An agent knows exactly what is being mutated and under what lifecycle condition.

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?

Usage is implied by 'before shipping' and 'pending move', which tells the agent the move must be in a pre-ship state, but no alternative tool is named or excluded. There is no explicit guidance on when to choose this over redraft_output or review_move, leaving routing to inference.

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