Skip to main content
Glama

Take Launchpad page offline or back online

launchpad_set_offline
Idempotent

Take the launch page offline (offline: true) or put it back online (offline: false). Offline is not deleting: the page, its design and its signups stay. While offline, visitors to the launch page address are sent to Your page if it is published, otherwise to hollerpost.com. Putting it back online shows the last approved page; it does not republish. Ask the person first; requires confirm: true after their yes. 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": {
      "offline": "<offline>",
      "confirm": "<confirm>"
    },
    "name": "launchpad_set_offline"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue only after the person approved this change.
offlineYestrue to take the launch page offline, false to put it back online.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that signups and design survive, that visitors are redirected to Your page if published and otherwise to hollerpost.com, that coming online does not republish, and that a 'draft' API key scope is required. The destructiveHint=false annotation is reinforced rather than merely repeated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the mode mapping, then layered with the most decision-relevant facts (non-destructive, redirect target, no republish, human approval). Every sentence carries information; nothing is filler.

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 two-parameter state toggle with no output schema, it covers everything an agent needs: both mode semantics, side effects on visitors, persistence guarantees, approval workflow, and auth scope.

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 schema already defines both fields; the description still adds meaning by tying offline:true/false to the visible consequences of each mode and framing confirm as post-approval acknowledgement rather than a generic flag.

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 (take offline / put back online) against a specific resource (the launch page), and immediately bounds it: 'Offline is not deleting' and 'it does not republish', which separates it from deletion and from the sibling go_live/republish path.

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?

Gives a clear operating condition — 'Ask the person first; requires confirm: true after their yes' — and implicitly routes republishing elsewhere by noting that coming back online 'shows the last approved page; it does not republish'. It never names a sibling alternative explicitly, so it stops short of a full when-to-use map.

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