Skip to main content
Glama

Update Launchpad draft

launchpad_update
Idempotent

Save the launch page's headline, pitch, count visibility, launch note, first button (a link or Your page) or mode (waitlist, to flip back from live). Optional design: build the page from blocks (advanced editor): hero, text, image, button, list, countdown (launch date), faq, social, divider, spacer and exactly one signup block. design replaces the saved design; read launchpad_get (launch_page.design) first. design.mode simple returns to the simple page and keeps the blocks. Omitted fields stay unchanged. Saves a draft only, including when an older approved page is public. Does not publish; the same automatic checks run on publish. Your page is not changed. Use launchpad_get to read the saved launch note and first button before asking the person to go live. Requires API key scope: draft.

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": "launchpad_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
designNoAdvanced editor design. Example: {"style":{"accentColor":"#C2410C"},"blocks":[{"type":"hero","headline":"Fresh loaves are coming","text":"Sourdough on Elm Street."},{"type":"countdown","date":"2026-12-06","show_days":true},{"type":"signup","button_label":"Save my spot"},{"type":"faq","items":[{"question":"Where?","answer":"12 Elm Street."}]}]}
show_countNo
launch_noteNo
primary_labelNoButton words when primary_target is page.
primary_targetNoWhere the live first button goes: link (primary_link_id) or page (the workspace's Your page, shown only while Your page is published).
waitlist_pitchNo
primary_link_idNoAn enabled, safe HTTPS page link in this workspace. Live mode needs it unless primary_target is page; null clears it.
waitlist_headlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / design / properties / style / properties / motion
      Added value: +{
      +  "description": "How much the page moves. lively (default): gentle entrance, button lift, signup shine, a small celebration on joining. subtle: soft fade and small hover lifts. off: no movement. Visitors who ask their device for reduced motion always get none.",
      +  "enum": [
      +    "lively",
      +    "subtle",
      +    "off"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description discloses that omitted fields stay unchanged, that the save is draft-only even when an older approved page is public, that design replaces the whole saved design, that the contrast rule is enforced server-side ('the API refuses less'), and that off-host images are refused. That is substantial mutation-safety context the annotations alone cannot convey.

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 front-loaded with the writable fields and then the design rules, with no filler sentences. It is somewhat run-on and repeats the draft-only idea twice ('Saves a draft only' and 'Saves a draft only, including when...'), which costs a point on tightness rather than clarity.

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?

With 9 parameters, a deeply nested design object, and no output schema, the description does well: it covers block composition rules, replacement semantics, id preservation, draft scope, and permission requirements. It stops short of describing what a successful save returns or what validation errors look like beyond the contrast and image-host refusals.

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 description coverage is only 44%, so the description must compensate, and it largely does: it explains design.mode 'simple' reverting to the simple page while keeping blocks, the 'exactly one signup block' rule, the at-most-one hero/countdown/social limits, the available block types, and keeping ids from launchpad_get. Fields like show_count, waitlist_headline, and waitlist_pitch are only named, not explained, which keeps it below a 5.

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 opens with a precise verb and resource ('Save the launch page's headline, pitch, count visibility, launch note, first button... or mode') and enumerates exactly which fields are writable. It also distinguishes this draft-saving operation from publishing ('Does not publish'), separating it from launchpad_go_live without needing the schema.

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?

It gives clear conditions: read launchpad_get (launch_page.design) first before replacing a design, and use launchpad_get to read the saved launch note and first button before asking the person to go live. It also states the prerequisite scope ('Requires API key scope: draft'). What it lacks is an explicit statement of when to use launchpad_go_live instead, though 'Does not publish' strongly implies it.

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