Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

View growth moves

list_feed
Read-only

The ranked backlog of growth marketing moves prepared for this product across SEO, AI visibility (GEO), competitors and distribution: title, why, area, status, rank, whether readable full-draft material is waiting (has_draft), and draft_kind (a full draft, a brief to complete, or null). It also carries posture: who may do it, act (you can), draft_only (you draft, a person posts) or founder_voice (the founder only). Read it before improvising growth work of your own. The material BODY is not here. Live moves only unless you pass include_resolved; pass since for what is new while the deep scan adds moves. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoISO-8601. Returns only moves first seen after it. Pass the newest first_seen_at you already hold so a move is never returned twice.
verbosityNoDefault 'compact': no material bodies, so a long list stays cheap to read; has_draft and draft_kind say whether each move carries an inspectable artefact, an assignment, or nothing readable. Use 'full' only when you need every body at once.
include_resolvedNoInclude resolved moves (shipped, skipped, archived, expired) as well as the live ones. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / verbosity / description
      Previous value: -"Default 'compact': no material bodies, so a long board stays cheap to read; has_draft and draft_kind say whether each move carries an inspectable artefact, an assignment, or nothing readable. Use 'full' only when you need every body at once."New value: +"Default 'compact': no material bodies, so a long list stays cheap to read; has_draft and draft_kind say whether each move carries an inspectable artefact, an assignment, or nothing readable. Use 'full' only when you need every body at once."
  2. Changed1 schema field changed
    • changedInput schema / properties / verbosity / description
      Previous value: -"Default 'compact': no drafted bodies, so a long board stays cheap to read, and has_draft says which moves have one. Use 'full' only when you need every body at once."New value: +"Default 'compact': no material bodies, so a long board stays cheap to read; has_draft and draft_kind say whether each move carries an inspectable artefact, an assignment, or nothing readable. Use 'full' only when you need every body at once."
  3. Changed3 schema fields changed
    • changedInput schema / properties / include_resolved / description
      Previous value: -"When true, include resolved moves (shipped, skipped, archived, expired) alongside the live ones. Default false: live moves only."New value: +"Include resolved moves (shipped, skipped, archived, expired) as well as the live ones. Default false."
    • changedInput schema / properties / since / description
      Previous value: -"Optional ISO-8601 timestamp. When set, return only moves first seen after it, the incremental \"what is new\" pull. Pass the newest first_seen_at you have already read so the same move is never returned twice."New value: +"ISO-8601. Returns only moves first seen after it. Pass the newest first_seen_at you already hold so a move is never returned twice."
    • addedInput schema / properties / verbosity
      Added value: +{
+  "description": "Default 'compact': no drafted bodies, so a long board stays cheap to read, and has_draft says which moves have one. Use 'full' only when you need every body at once.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional ISO-8601 timestamp. When set, return only moves first seen after it, the incremental \"what is new\" pull. Pass the newest first_seen_at you have already read so the same move is never returned twice.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/destructive/openWorld, and the description confirms 'Read-only' plus adds real context beyond them: the material BODY is absent, live moves only by default, and compact verbosity omits bodies to keep long lists cheap. It does not discuss rate limits or pagination, but the filtering defaults are well disclosed.

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?

It is dense and front-loaded, leading with what the backlog contains before the caveats about filtering and the missing body. Slightly long, and 'Read-only' duplicates the annotations, but nearly every clause carries information.

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, the description carries the return-shape burden and does so by enumerating the fields and posture values, plus flagging that bodies are excluded. An agent could call it correctly, though the exact response shape and ordering guarantees are only partially specified.

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 the schema already documents since, verbosity, and include_resolved thoroughly. The description's field-level prose (has_draft, draft_kind, posture) describes return values rather than adding meaning to the parameters themselves, so the baseline 3 applies.

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 names a specific verb and resource ('the ranked backlog of growth marketing moves') and enumerates the fields returned (title, why, area, status, rank, has_draft, draft_kind, posture). It is clearly distinguishable from siblings like get_move, replenish_feed, or get_content_calendar.

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?

It gives explicit context ('read it before improvising growth work of your own') and states the conditions for include_resolved and since. It does not name alternative tools for fetching a single move or the missing body material, so routing is implied rather than explicit.

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