Skip to main content
Glama

Create a launch draft

create_launch_draft

Start a new launch on ShipDesk.dev as a private draft. Give at least one link: website, app_store or google_play. Name, one line, description and tags are read from the website when left out. Returns the draft with an edit_link where the maker picks a launch day and sends it in.

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

Input Schema

NameRequiredDescriptionDefault
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

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers key behavior: the result is private, not published ("the maker picks a launch day and sends it in"), fields are auto-derived from the website when omitted, and the response includes an edit_link. It omits auth requirements and rate limits, which keeps it off a 5.

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 tight sentences: what it creates, the input rule, then the fallback/return behavior. The essential constraint is front-loaded with zero 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 7-param mutation tool with no annotations and no output schema, the description covers the required-link rule, the auto-derivation of four optional fields, and the shape of the return (draft plus edit_link). Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description adds a cross-parameter constraint the schema cannot express (required=[], yet at least one of website/app_store/google_play must be supplied) and the auto-fill rule for name, one_line, description and tags when left out.

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 and resource ("Start a new launch"), plus the scope ("as a private draft"), which cleanly separates it from the sibling update_launch_draft and from add_screenshot. An agent can tell what this creates without opening 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?

Gives a concrete precondition ("Give at least one link: website, app_store or google_play") and implies the create-vs-modify split through the word "new". It stops short of naming update_launch_draft as the alternative for existing launches or stating exclusions.

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