Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

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: call get_move for the one you are working on. Live moves only unless you pass include_resolved; pass since for what is new while the deep scan fills the board. 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 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.
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 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."
  2. 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds meaningful behavior beyond annotations: default filtering to live moves, incremental use of since during a deep scan, and the semantic of draft_kind/posture. It does not mention pagination or rate limits, but for a read-only list tool this is sufficient.

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 dense and front-loaded: it opens with what the feed contains, then covers posture, usage, the get_move routing, and filtering. Every sentence carries useful information. It is longer than strictly necessary and slightly redundant with the schema in a couple of spots, but it remains well structured and efficient.

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?

Since there is no output schema, the description takes on the work of enumerating the main output fields and their meanings, which it does well. It also explains the relationship to get_move for material bodies. It does not name every possible output field such as the move ID or first_seen_at, but it provides enough for an agent to call and consume the tool correctly.

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 description has little obligation to document parameters. All three parameters (since, verbosity, include_resolved) are already thoroughly described in the schema. The description adds some contextual rationale for since and verbosity, but does not substantially extend what the schema already provides.

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 clearly identifies the resource as the 'ranked backlog of growth marketing moves' and enumerates the fields returned (title, why, area, status, rank, has_draft, draft_kind, posture). It also distinguishes itself from get_move by explicitly stating that the material body is elsewhere. The purpose is unambiguous and strong.

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?

It says exactly when to use it: 'Read it before improvising growth work of your own.' It also tells the agent to call get_move for the material body, providing a clear alternative. The use of include_resolved and since are explained with concrete conditions ('Live moves only unless...', 'pass since for what is new...').

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