craft-gtm-mcp

Launch Commander

launch_commander

Read-only

Helps you decide your launch plan: it takes what you are launching, the launch type, your target segments and your goals, and returns a phased launch plan with tasks, a messaging table and success metrics. Give a date for a dated timeline, or 'TBD' or a quarter such as 'Q2 2027' for a flexible plan. Tasks and messaging follow the sector and business model read from your inputs, and each goal is filed under its own metric.

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": {
      "product_feature": "<product_feature>",
      "launch_type": "<launch_type>",
      "target_segments": "<target_segments>",
      "goals": "<goals>"
    },
    "name": "launch_commander"
  }
}

Input Schema

Name	Required	Description
`goals`	Yes	Launch success metrics (for example '40 qualified meetings, $300K pipeline, 5 reference customers')
`industry`	No	Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read
`team_size`	No	Marketing/GTM team size affects task distribution
`launch_date`	No	Target launch date. Accepts: 'YYYY-MM-DD', 'Q1 2027', 'March 2027', or 'TBD' for planning mode
`launch_type`	Yes	Type of launch determines plan complexity
`your_sector`	No	Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear.
`budget_level`	No	Budget affects recommended tactics
`business_model`	No	Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it
`product_feature`	Yes	What you're launching (product/feature name and description)
`target_segments`	Yes	Target customer segments (comma-separated)
`available_channels`	No	Optional: Marketing channels available (comma-separated). E.g., 'email, linkedin, blog, webinar, PR, paid_ads, community'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / industry / description

Previous value: -"Optional: the sector you sell into, so the answer uses that sector's buyers, measures and objections. Leave it out and the tool reads the sector from your other inputs and names what it read"New value: +"Optional: your own company's sector, so the answer uses the usual buyers, measures and objections for what you sell. Leave it out and the tool reads the sector from your other inputs and names what it read"

First observedOct 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the lower bar applies. The description adds genuine behavioral context: tasks and messaging are derived from the sector and business model read from the inputs, each goal is filed under its own metric, and when no sector is supplied the tool infers it and names what it read (or stays neutral if unclear) – useful disclosure of inference behavior for an agent.

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?

Four sentences, front-loaded with the what and the return shape before the input-format detail; there is little waste. Some content repeats the schema (date formats, sector fallback), which would be the first thing to cut.

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 11-parameter planning tool with no output schema, the description usefully characterizes the return value (phased plan, task list, messaging table, per-goal metrics) and explains how optional inputs influence the output. The remaining gap is the duplicate industry/your_sector parameters, which an agent must resolve without help from the description.

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 coverage is 100% and six parameters carry enums, so the schema already documents formats like 'TBD'/'Q2 2027' and the enum values. The description restates the date-format rule and the sector-inference behavior but adds no meaning beyond the schema, and it does not clarify the apparent overlap between the 'industry' and 'your_sector' parameters, which both enumerate the same values.

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?

The description names the verb and resource plainly (decide a launch plan from product/feature, launch type, segments and goals) and enumerates the outputs: a phased plan with tasks, a messaging table and success metrics. That output signature is distinctive among siblings such as craft_gtm_analyzer or competitive_intel, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage guidance is confined to one input mode: supply a date for a dated timeline, or 'TBD'/'Q2 2027' for a flexible plan. There is no when-to-use versus when-not-to-use guidance relative to the other GTM planning tools, and no prerequisite or scope statement telling an agent when this is the wrong pick.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All craft-gtm-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.