Skip to main content
Glama

AfterLaunch: the agentic growth marketing engine

by io.afterlaunch

ship_move

Mark a growth move shipped (the same action as Ship in the Feed). WHEN: call it the moment the founder confirms the work is actually live, with their go and never on your own. Shipping is the human's decision; reporting the ship is yours, and it is not optional: AfterLaunch measures what happens after a move goes live, so an unreported ship is work the record never sees. Report only what is true: drafted, staged and awaiting review are not shipped, and a move the founder turned down goes to skip_move with the real reason. Free; requires the 'act' scope. Pass asset_url when the move published a live asset. The reply carries receipt_url when the move has a tracked link: a public, shareable permalink to its receipt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
move_idYesMove id (uuid), from list_feed.
asset_urlNoOptional confirmed live URL of the shipped asset.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate a non-read-only, non-destructive mutation. The description adds crucial behavioral context: shipping is a human decision, reporting is the agent's non-optional duty, after-launch measurements depend on the report, and a receipt_url will be returned when a tracked link exists. This goes far beyond the annotation profile without contradicting it.

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?

Though it is a longer description, every sentence contributes essential operational nuance: the when, the exclusions, scope requirements, optional param, and return value. It is front-loaded with the core purpose, then structured to cover exceptions and constraints without redundancy.

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

Completeness5/5

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

The tool has only two parameters and no output schema, yet the description still explains the return behavior (receipt_url) and all relevant lifecycle rules. It differentiates from skip_move and provides decision-making context, making it complete for an agent to invoke correctly.

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 100%, so baseline is 3. The description adds value by clarifying the conditional use of asset_url ('Pass asset_url when the move published a live asset'), which the schema does not fully convey. While move_id is straightforward, the added conditional guidance elevates the score.

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 opens with a specific verb and resource: 'Mark a growth move shipped', and explicitly references 'the same action as Ship in the Feed' for clarity. It also distinguishes from sibling skip_move by stating that turned-down moves go there, making the purpose unmistakable.

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

Usage Guidelines5/5

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

Provides explicit WHEN: 'call it the moment the founder confirms the work is actually live, with their go and never on your own.' It also states exclusions (drafted/staged/awaiting review are not shipped) and names the alternative tool skip_move for rejected moves. This is model guidance for when to use this vs alternatives.

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

All AfterLaunch: the agentic growth marketing engine toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools follow a clear action+resource pattern (get_, list_, set_, ship_, etc.) with distinct purposes. A few boundaries could cause confusion, such as get_move vs get_output (both return drafts) and ship_move vs set_output_status (both mark things shipped), though descriptions mitigate this sufficiently.

Naming Consistency4/5

The overwhelming majority use consistent snake_case verb_noun naming (list_feed, ship_move, get_visibility). The only outlier is 'whoami', a common convention but not verb_noun; otherwise the pattern is highly predictable.

Tool Count2/5

At 41 tools, the surface is well over the 25-tool threshold for 'too many'. While the domain is broad, this volume places significant cognitive load on agents and suggests some consolidation or modularization could help.

Completeness3/5

Core workflows for moves and outputs are covered (create/list/get/update/ship/skip/undo). However, the tool descriptions reference 'approve_output' as the publishing action, yet that tool is absent from the list, leaving a dead end for channel distribution. There are also no tools for editing competitors or managing Memory pages beyond recording insights.

Resources