Skip to main content
Glama

Start the 90-day Agentic Launch (prepares outreach - never auto-sends)

start_agentic_launch
Idempotent

Kick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report. Demand Discovery surfaces named prospects matching the idea's ICP and DRAFTS the first outreach batch. It sends NOTHING automatically - the user reviews and sends from their hosted manage page. Outreach is drafted to come from Amy @ Demand Discovery, with replies routed to the user's own email.

Demand Discovery’s main deliverable is real people describing your idea, each quote linked to the source, followed by ready-to-post replies to those people.

Call this after a paid report is "ready" and the user wants to act on it (e.g. "generate prospects", "start agentic launch", "find me people to talk to", "yes, do the outreach"). Pass the reportId, the user's email, and the alTriggerToken from the ready report if you have it. The email MUST be the address the user themselves provided earlier in this conversation (their report-delivery email) - if you don't have it in context, ask the user first; NEVER invent one or use a placeholder like user@example.com (placeholders are rejected and the launch will not start). The response returns a manageUrl where the user reviews/sends the drafted outreach (and can switch the sender to their own Gmail).

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": {
      "reportId": "<reportId>",
      "email": "<email>"
    },
    "name": "start_agentic_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesREQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here. Reuse the EXACT address the user gave earlier in this conversation for report delivery; if you don't have it, ask the user. NEVER invent one or substitute a placeholder (e.g. user@example.com) - placeholders are rejected.
reportIdYesREQUIRED. The reportId of the completed (ready) Demand Discovery Report.
alTriggerTokenNoOptional pass-through token from the ready report payload (report.alTriggerToken), if available.

Output Schema

NameRequiredDescriptionDefault
alIdNoThe Agentic Launch handle, if started.
senderYesAlways 'amy' for inline triggers.
statusYesstarted | queued | error | unconfigured_fallback | error_fallback | needs_real_email | email_not_owner.
startedYesTrue if Agentic Launch was started (prospects generated + outreach drafted, awaiting the user's review-and-send).
manageUrlYesWhere the user reviews and SENDS the drafted outreach, and manages the 90-day launch. Nothing goes out until they do.
nextActionYesWhat the user should do next.
productUrlYes
replyToEmailYesWhere Amy forwards replies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / replyToEmail / description
      Previous value: -"Where Allison forwards replies."New value: +"Where Amy forwards replies."
    • changedOutput schema / properties / sender / description
      Previous value: -"Always 'allison' for inline triggers."New value: +"Always 'amy' for inline triggers."
  2. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"REQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here."New value: +"REQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here. Reuse the EXACT address the user gave earlier in this conversation for report delivery; if you don't have it, ask the user. NEVER invent one or substitute a placeholder (e.g. user@example.com) - placeholders are rejected."
    • changedOutput schema / properties / status / description
      Previous value: -"started | queued | error | unconfigured_fallback | error_fallback."New value: +"started | queued | error | unconfigured_fallback | error_fallback | needs_real_email | email_not_owner."
  3. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"REQUIRED. The user's email - replies to the drafted outreach route here."New value: +"REQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here."
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare non-destructive and idempotent, and the description adds context annotations cannot: nothing is auto-sent, the user reviews/sends from a hosted manage page, drafted outreach comes from 'Amy @ Demand Discovery', replies route to the user's own address, and the sender can be switched to their Gmail. It also discloses the manageUrl return and the hard rejection of placeholder emails, which is exactly the kind of behavioral detail an agent needs before invoking.

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?

Front-loaded with the action and its key constraint (never auto-sends), and the ordering of prerequisite, arguments, and return value is easy to scan. It loses a point for the promotional aside about Demand Discovery's 'main deliverable' and for repeating the placeholder-email warning that the schema already carries verbatim.

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 mutation-style launch tool with an output schema, the description covers prerequisites, required arguments, the email-provenance rule, and where the user acts afterward. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters are already documented with the same warnings about the user's own email and the optional alTriggerToken. The description restates this guidance rather than adding format, sourcing, or edge-case meaning beyond the schema, so the baseline 3 applies.

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 ('Kick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report') and immediately clarifies the actual effect: it drafts the first outreach batch and sends nothing. That scope statement separates it from sibling start_demand_report (which produces the report) without requiring the agent to open either 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 clear precondition ('after a paid report is "ready"') plus concrete user-intent triggers ('generate prospects', 'start agentic launch', 'find me people to talk to'). It does not name an alternative for the not-ready case (e.g. checking report status), so the when-not path is implied rather than explicit.

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