Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

View growth moves

list_feed
Read-only

Use this when the user asks for growth ideas or their next move, or their standing orders call for it. Returns the ranked growth moves across SEO, AI visibility, competitors and distribution: title, why, area, status and rank, has_draft and draft_kind (a full draft, a brief to complete, or null), and posture: who may do it, act (you can), draft_only (you draft, a person posts) or founder_voice (the founder only). 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_feed"
  }
}

Input 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.6/5.0
Behavior4/5

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

Annotations already cover the read-only and closed-world safety profile, yet the description adds substantive behavior: default exclusion of resolved moves, the absence of material BODY, and the posture meanings (act vs draft_only vs founder_voice) that govern what the agent may do with a result. The trailing 'Read-only' merely restates the annotation rather than adding to it.

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?

Front-loaded with the usage trigger, then the return shape, then caveats and parameter modifiers — a sensible order. Dense but every clause carries information; only the closing 'Read-only' and the restated include_resolved default are redundant with structured fields.

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?

There is no output schema, and the description compensates by naming the exact fields returned and, critically, flagging that material bodies are absent by default. That omission note is what prevents an agent from calling this expecting full draft content.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that 'since' exists for incremental polling 'while the deep scan adds moves' — the reason the field is safe to reuse. The include_resolved and verbosity clauses largely restate the schema descriptions verbatim.

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?

States a specific verb and resource: 'Returns the ranked growth moves across SEO, AI visibility, competitors and distribution', then enumerates the returned fields. An agent can tell this apart from single-item siblings like get_move without opening any schema.

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?

Names the trigger explicitly ('when the user asks for growth ideas or their next move, or their standing orders call for it') and gives conditions for each optional parameter: include_resolved only for archived/shipped items, since for incremental scanning during a deep scan, verbosity 'full' only when every body is needed at once.

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