Skip to main content
Glama

Launch voice campaign

launch_voice_campaign
Destructive

LAUNCH a voice campaign: the AI agent starts calling its contacts for real (or at scheduled_at, if it has one, and then the status is scheduled). Calls go to real people, inside the calling window and the account's compliance rules, and use AI minutes. consent_attested must be true, and it is a legal statement: the person launching attests that EVERY contact in the list consented to receive calls from an AI agent (the FCC's 2024 ruling treats AI voices as artificial under the TCPA). It is recorded under the user this connection acts as, with the time. It is true only when the person launching has said so. A draft or scheduled campaign can be launched; a refusal (no consent, invalid contacts, line unable to call, minutes cap reached) is explained and nothing starts.

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": {
      "campaign_id": "<campaign_id>",
      "consent_attested": "<consent_attested>"
    },
    "name": "launch_voice_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesCampaign id as returned by list_voice_campaigns.
exclude_invalidNotrue ONLY when the person launching confirmed that contacts with an invalid phone number are left out of the launch (they are not called and stay in the report). Without it, a list with invalid contacts is refused with their count.
consent_attestedYestrue: every contact consented to AI-agent calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / exclude_invalid
      Added value: +{
      +  "description": "true ONLY when the person launching confirmed that contacts with an invalid phone number are left out of the launch (they are not called and stay in the report). Without it, a list with invalid contacts is refused with their count.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes far beyond the annotations by disclosing that calls reach real people, run inside the calling window and account compliance rules, consume AI minutes, and that the attestation is recorded under the acting user with a timestamp. It also enumerates the refusal causes (no consent, invalid contacts, line unable to call, minutes cap) and guarantees nothing starts on refusal, which is exactly the operational context an agent needs for a destructive write.

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?

The action and its immediate effect are stated first, then preconditions, then refusal behavior — a sensible order. The paragraph is dense with stacked parentheticals and could be broken into shorter sentences, but no sentence is filler.

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 a non-idempotent, destructive mutation with no output schema, the description covers consequences, prerequisites, and failure modes thoroughly. It never states what a successful launch returns (campaign id, resulting status), leaving the agent to infer the response shape.

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 schema already defines all three parameters; the description nonetheless adds legal and audit meaning to consent_attested (it is an attestation the launcher has actually said so, recorded under the acting user, tied to the FCC 2024 ruling). exclude_invalid is left entirely to the schema description, which keeps this from a 5.

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?

Front-loads a specific verb and resource ("LAUNCH a voice campaign") and immediately defines the effect: the AI agent starts calling contacts for real. This clearly separates it from siblings like test_call_voice_campaign, pause_voice_campaign, resume_voice_campaign, and cancel_voice_campaign.

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?

Explains the precondition (consent_attested must be true), the eligible states (a draft or scheduled campaign can be launched), and what happens when the launch is refused. It stops short of explicitly naming alternatives such as testing with test_call_voice_campaign before launching or pausing with pause_voice_campaign, so routing guidance is implied rather than stated.

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