Skip to main content
Glama

Launchpad go live

launchpad_go_live
Destructive

Switch the launch page to live mode and request publication after automatic checks. First use launchpad_get, show the person the saved launch note and primary link (the first button: its label and where it goes, a link or Your page), and wait for a clear yes. Requires confirm: true after that approval and a claimed handle with an enabled safe HTTPS primary link or primary_target page. A pending_review or review_pending hold is not live: explain owner_reason, do not retry or bypass review. If launchpad_get shows offline: true, the page stays offline until launchpad_set_offline with offline: false. Sends no campaign. Requires API key scope: draft.

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": {
      "confirm": "<confirm>"
    },
    "name": "launchpad_go_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue only after the person saw the launch note and primary link and approved going live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and the description confirms the mutation and adds real context beyond them: the operation may resolve to a held pending_review state rather than live, review holds must not be bypassed, and it sends no campaign. It also names the required API key scope (draft). Slightly short of a 5 only because the 'automatic checks' are not itemized and the observable result beyond the hold case isn't spelled out.

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 action is front-loaded in the first clause, followed by prerequisites, exception handling, and side effects in a logical order. It is dense and the parenthetical about the first button's label and destination is awkwardly packed, but every sentence carries operational information rather than padding.

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?

For a mutating launch tool with no output schema, the description covers what is required, what is prohibited, the three plausible outcomes (live, review hold, offline), and the auth scope. An agent has enough to call it correctly and to report results without guessing.

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?

There is a single parameter with 100% schema description coverage, and the schema's description already states that confirm is true only after the person saw the note and link and approved. The description restates that gate rather than adding syntax or edge-case meaning, so it sits at the baseline for a fully documented single param.

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?

Opens with a concrete verb and resource: 'Switch the launch page to live mode and request publication after automatic checks.' The reader immediately knows this is a state-change on the launch page, distinct from launchpad_set_offline and launchpad_update, both of which the description implicitly routes away from by naming the offline flag and the get step.

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?

Explicit sequencing and exclusions: call launchpad_get first, show the launch note and primary link, wait for a clear yes, then pass confirm: true. It also states when NOT to proceed (pending_review/review_pending → explain owner_reason, do not retry or bypass; offline true → requires launchpad_set_offline first). Sibling alternatives are named with the condition that selects each.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources