AfterLaunch

Record content

record_content

Destructive

File a growth idea (optional channels, kind, score, final_text sent verbatim, desk: a post, reply or task the owner posts by hand, queued at slot_at, or a decision or read that needs the owner, due_on a date), original X draft or research outcome. Research appends a result to its idea; send expected_updated_at unchanged from the calendar. It keeps evidence holds and never authorises drafting. Requires 'act' scope; no spend or posting. Keep run_key stable. Drafts need action_kind social_post and one idea_id or source_idea; source_url is evidence. adopt_legacy only reclassifies an exact saved replay (a reply keeps its X destination).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`why`	No
`text`	No
`title`	No
`channel`	No
`idea_id`	No
`run_key`	No
`research`	No
`claim_ids`	No
`operation`	Yes
`source_url`	No
`action_kind`	No
`source_idea`	No
`adopt_legacy`	No
`expected_updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026
- addedInput schema / properties / source_idea / properties / desk / properties / note
```
Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
```
- addedInput schema / properties / source_idea / properties / desk / properties / venue
```
Added value: +{
+  "enum": [
+    "hn",
+    "producthunt",
+    "reddit",
+    "email"
+  ],
+  "type": "string"
+}
```
Changed5 schema fields changedOct 15, 2026
- addedInput schema / properties / source_idea / properties / desk / properties / due_on
```
Added value: +{
+  "format": "date",
+  "type": "string"
+}
```
- changedInput schema / properties / source_idea / properties / desk / properties / kind / enum
```
Previous value: -[
-  "post",
-  "reply",
-  "task"
-]New value: +[
+  "post",
+  "reply",
+  "task",
+  "decision",
+  "read"
+]
```
- addedInput schema / properties / source_idea / properties / desk / properties / source
```
Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
```
- addedInput schema / properties / source_idea / properties / desk / properties / step
```
Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
```
- addedInput schema / properties / source_idea / properties / desk / properties / why
```
Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
```

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / source_idea / properties / series

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "ends_on": {
+      "format": "date",
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "major_drop",
+        "minor_drop",
+        "posts",
+        "free_tool",
+        "launch",
+        "announcement",
+        "experiment_writeup"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "maxLength": 120,
+      "minLength": 1,
+      "type": "string"
+    },
+    "starts_on": {
+      "format": "date",
+      "type": "string"
+    },
+    "why": {
+      "maxLength": 200,
+      "type": "string"
+    }
+  },
+  "required": [
+    "name"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / source_idea / properties / desk

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "first_reply": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "image": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "post",
+        "reply",
+        "task"
+      ],
+      "type": "string"
+    },
+    "slot_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "target_url": {
+      "format": "uri",
+      "maxLength": 2048,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / source_idea / properties / final_text

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "channel": {
+      "enum": [
+        "x",
+        "linkedin"
+      ],
+      "type": "string"
+    },
+    "text": {
+      "maxLength": 20000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "channel",
+    "text"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedSep 15, 2026

addedInput schema / properties / source_idea / properties / channels

Added value: +{
+  "items": {
+    "enum": [
+      "x",
+      "linkedin",
+      "article",
+      "seo"
+    ],
+    "type": "string"
+  },
+  "maxItems": 4,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / source_idea / properties / kind

Added value: +{
+  "enum": [
+    "opinion",
+    "educational",
+    "amplify"
+  ],
+  "type": "string"
+}

addedInput schema / properties / source_idea / properties / score

Added value: +{
+  "maximum": 10,
+  "minimum": 0,
+  "type": "number"
+}

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / expected_updated_at

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

changedInput schema / properties / operation / enum

Previous value: -[
-  "idea",
-  "draft"
-]New value: +[
+  "idea",
+  "draft",
+  "research"
+]

addedInput schema / properties / research

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "limitations": {
+      "maxLength": 5000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "method": {
+      "maxLength": 5000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "outcome": {
+      "enum": [
+        "supported",
+        "not_supported",
+        "inconclusive"
+      ],
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "observed_at": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "title": {
+            "maxLength": 300,
+            "minLength": 1,
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "maxLength": 2048,
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url",
+          "observed_at"
+        ],
+        "type": "object"
+      },
+      "maxItems": 50,
+      "type": "array"
+    },
+    "summary": {
+      "maxLength": 5000,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "outcome",
+    "summary",
+    "method",
+    "limitations",
+    "sources"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 11, 2026

addedInput schema / properties / adopt_legacy

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "action_kind": {
+      "enum": [
+        "social_post",
+        "community_reply"
+      ],
+      "type": "string"
+    },
+    "output_id": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "required": [
+    "output_id",
+    "action_kind"
+  ],
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare a mutating, destructive, non-open-world tool, and the description adds real context beyond them: it requires the 'act' scope, performs no spend or posting, keeps evidence holds, does not authorise drafting, requires run_key to stay stable (idempotency) and expected_updated_at to be passed unchanged (optimistic concurrency). That is meaningful disclosure the annotations cannot carry.

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

Conciseness3/5

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

The leading clause is front-loaded with the main verb, which is good, but the first sentence buries a parenthetical inside a parenthetical ('desk: a post, reply or task ... due_on a date') that is hard to parse. Length is moderate and largely earns its place, yet the structure is a run-on rather than cleanly grouped per operation.

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?

For a 14-parameter, deeply nested mutation tool with no output schema and only three sparse annotations, the description covers the operation-specific requirements and idempotency/concurrency contract well. It still leaves several parameters and the research sub-object's required fields unexplained, so an agent would have to infer field-level semantics from the schema alone.

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 0%, so the description must carry parameter meaning, and it covers much ground — channels, kind, score, final_text verbatim, desk/slot_at/due_on, source_idea, action_kind, idea_id, source_url, run_key, expected_updated_at, adopt_legacy. But top-level 'why', 'text', 'title', 'channel', 'claim_ids', and the research object's required fields are never explained, so a large share of the 14 params remains undocumented in both places.

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 ('File') and resource set — a growth idea, an original X draft, or a research outcome — which maps to the operation enum and distinguishes it from read-side siblings like get_content_calendar. The parenthetical stuffing and nested clauses blur the core purpose somewhat, but an agent can still identify it as the writer for content artifacts.

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?

Gives conditional guidance for individual operations ('Research appends a result to its idea', 'Drafts need action_kind social_post and one idea_id or source_idea', 'adopt_legacy only reclassifies an exact saved replay'). However it never states when to pick this over sibling writers such as update_draft, redraft_output, or set_output_status, so alternative selection is left implicit.

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

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

Need Help?