Skip to main content
Glama

Get Launchpad

launchpad_get
Read-onlyIdempotent

Read the Launchpad card: confirmed_signups, emailable_subscribers, awaiting_confirmation, confirmed this week and queued confirmations, confirmation allowance, list size versus plan emails, share URL, launch_url, main_page, offline (true while the owner has taken the launch page offline) and the launch page's saved settings (launch_page: launch note, first button, published, offline, design: the advanced editor blocks or null). The launch page is separate from Your page; main_page says which one hollerpost.com/@handle shows. custom_domain (when the feature is on): the launch page's own address, its status (waiting_dns, securing, live, error), the fix for an error and the CNAME record to add. Requires API key scope: read.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds information the annotations do not: the required API key scope ('read'), an explanation of the offline flag's meaning (true while the owner has taken the launch page offline), and how custom_domain status values (waiting_dns, securing, live, error) should be interpreted. Return format is only hinted at, but that is beyond the annotation burden.

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

Conciseness3/5

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

The critical information is front-loaded, but the body is one sprawling sentence that packs confirmed_signups, emailable_subscribers, awaiting_confirmation, confirmation allowance, share URL, launch_url, saved settings, custom_domain status and CNAME data into a single run-on list. Splitting the field inventory from the launch-page-versus-main-page clarification and from the auth note would make it far easier to scan.

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 no output schema, the field enumeration is the only description of what comes back, and it covers the main state, saved launch-page settings, the editor design blocks, and the custom-domain lifecycle including the error fix and CNAME. Adding the required scope completes the picture an agent needs to call it. Minor gaps remain around the shape of nested objects like design and launch_page settings.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies.

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?

Opens with a specific verb and resource ('Read the Launchpad card') and explicitly separates the launch page from 'Your page', noting main_page indicates which surface hollerpost.com/@handle shows — this distinguishes it from the sibling page_get. The remainder is a field inventory rather than a purpose statement, but the core purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as launchpad_update, launchpad_go_live or launchpad_set_offline, even though those mutating siblings make the read-first sequencing the obvious reason to call this. Usage can only be inferred from the read-only nature of the operation.

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