Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Track a question

track_prompt
Destructive

Add one customer question to the AI visibility (GEO) set AfterLaunch measures this product on. Free, spends nothing. Two honest consequences: the NEXT scheduled scan runs at full depth, and the week-over-week trend re-baselines, since two different question sets do not compare. So add deliberately. 10 to 200 characters, deduplicated, up to 50 on the Founder plan. Requires the 'config' scope and the Founder plan; on a free trial the questions stay readable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "track_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe customer question to track, as a person would ask an AI assistant, e.g. "What is the best invoicing tool for UK freelancers?".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"The buyer question to track, as a real person would ask an AI assistant, e.g. \"What is the best invoicing tool for UK freelancers?\"."New value: +"The customer question to track, as a person would ask an AI assistant, e.g. \"What is the best invoicing tool for UK freelancers?\"."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses that it is free, requires the 'config' scope and Founder plan, caps at 50 on Founder, and that free-trial questions remain readable. Annotations already flag destructiveHint=true, and the description concretizes exactly what is destroyed – the week-over-week trend baseline – which is the most valuable disclosure here.

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 action and consequence, and nearly every clause carries information (cost, scan depth, trend reset, limits, permissions). Minor inflation from framing phrases like "Two honest consequences" and "So add deliberately".

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?

Covers authorization, quota, cost, and side effects for a one-parameter mutation with no output schema. The only gap is that it does not say what the call returns (e.g., the created question or updated count), which matters slightly for an agent verifying success.

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% and the single param already documents length bounds and an example, so baseline is 3. The description adds meaning beyond the schema by stating deduplication and the per-plan quota, which the schema does not convey.

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?

Specific verb+resource: "Add one customer question to the AI visibility (GEO) set AfterLaunch measures this product on" tells an agent exactly what the tool does and the domain it operates on. It never names the inverse tool untrack_prompt, so the distinction is inferable rather than stated.

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 decision-relevant context ("So add deliberately") by explaining cost: the trend re-baselines and the next scan runs at full depth. However, it never states when NOT to add a question or points to untrack_prompt as the way to undo a deliberate-but-wrong add, leaving that to inference from sibling names.

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