Skip to main content
Glama

Launch a campaign

launch_campaign
DestructiveIdempotent

Use this when the user has confirmed that a campaign should start sending. Starts a draft campaign, or a paused one again with the messages it had queued. Real emails and LinkedIn messages then go out to the people on its lists, and a sent message cannot be taken back. It first runs the launch checks and refuses with the first that fails. Enrolling people runs in the background, so read the campaign afterwards to follow it. Launching a campaign that is already running changes nothing. Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "launch_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructive/openWorld/idempotent annotations, it discloses concrete consequences: real emails and LinkedIn messages go out, a sent message cannot be taken back, the first failed launch check aborts the call, and enrollment proceeds in the background so the campaign must be re-read. It also clarifies that re-launching a running campaign changes nothing, reinforcing the idempotent hint with specifics.

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?

The description is front-loaded with the triggering condition and the core action, then adds consequences and edge cases in short, information-dense sentences. No sentence is redundant padding; even the trailing 'Free' note carries a distinct piece of information.

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 destructive, open-world, fire-and-forget launch with no output schema, the definition covers the essential needs: precondition for use, irreversible side effects, validation behavior, the fact that results are asynchronous, and idempotency. An agent can invoke this safely without further documentation.

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?

The single campaignId parameter is fully documented in the schema (100% coverage), so the description does not need to restate its format or constraints. It adds nothing beyond the schema about the parameter, which is appropriate given that coverage but caps the score at the 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?

The description gives a precise verb and resource ('Starts a draft campaign, or a paused one again with the messages it had queued') and clarifies the scope of what gets launched. It distinguishes launch from the surrounding setup/list-management operations implicitly, but never names a sibling tool (e.g., resume or readiness-check) to sharpen the boundary.

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?

It states a clear precondition for use: 'Use this when the user has confirmed that a campaign should start sending.' It also explains that launch checks run first and that the tool is a no-op on an already-running campaign, which helps avoid misuse. It stops short of explicitly pointing at alternatives for related tasks.

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