Skip to main content
Glama

Update a launch draft

update_launch_draft

Change a draft's links, name, one line, description or tags. Only the fields you give change. A launch already in review or live can only change its one line, description and tags.

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": {
      "id": "<id>"
    },
    "name": "update_launch_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe launch id from create_launch_draft or my_launches
nameNothe product's name
tagsNoup to 3 categories
websiteNothe product's website, like example.com
one_lineNoone line about what it does, shown under the name on the board
app_storeNothe App Store link, like apps.apple.com/app/name/id123456789, or a TestFlight invite for an app in beta, like testflight.apple.com/join/AbC123xy
descriptionNowhat it does, who it is for and why it was built
google_playNothe Google Play link, like play.google.com/store/apps/details?id=com.example

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / app_store / description
      Previous value: -"the App Store link, like apps.apple.com/app/name/id123456789"New value: +"the App Store link, like apps.apple.com/app/name/id123456789, or a TestFlight invite for an app in beta, like testflight.apple.com/join/AbC123xy"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It usefully discloses sparse-update semantics (unspecified fields are left alone) and a state-based mutation restriction, but says nothing about required ownership/permissions, reversibility, or what a successful change returns — significant gaps for an unannotated mutation tool.

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?

Three short sentences, no filler, with the operation and its partial-update rule front-loaded and the state limitation placed last as a qualifier. Every sentence carries distinct information.

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?

For an 8-parameter mutation tool with full schema coverage and no output schema or annotations, the description covers what changes, how partial updates behave, and what is forbidden by state. The remaining omission is the response/confirmation behavior and any permission requirement, which keeps it short of 5.

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?

Schema description coverage is 100%, so every parameter (including maxLength, maxItems on tags, and link formats) is already documented. The description contributes one genuinely new per-parameter constraint — that name, website, app_store and google_play become inapplicable once a launch is in review or live — but it does not explain that mapping explicitly, so it stays near baseline.

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?

States a specific verb ("Change") and resource ("a draft") plus the exact mutable field set (links, name, one line, description, tags). It is clearly distinct from create_launch_draft in practice, but it never explicitly contrasts itself with any sibling, so it lands at 4 rather than 5.

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 real precondition the agent cannot get elsewhere: a launch already in review or live may only change one_line, description and tags. Combined with "Only the fields you give change," the agent knows both the partial-update contract and the state-dependent limit, though it never names when to prefer create_launch_draft instead.

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