Skip to main content
Glama

campaigns_create

Read-onlyIdempotent

Start a bulk outbound call campaign: dial a list of phone numbers with a voice agent, at a bounded concurrency, retrying no-answers. Phone network only (twilio/telnyx). It begins dialing on its own — no separate start.

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": {
      "name": "<name>",
      "phone_numbers": "<phone_numbers>"
    },
    "name": "campaigns_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCampaign name
channelNoCarrier (default telnyx).
agent_idNoVoice agent that makes the calls.
greetingNoFirst line the agent says on pickup.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
instructionsNoWhat the agent should do on the call.
max_attemptsNoRetries per number on no-answer (default 3).
phone_numbersYesNumbers to dial, E.164 (e.g. '+15551234567').
max_concurrentNoSimultaneous calls (default 2).
channel_account_idNoThe phone number the campaign calls from (id from channels.list). OMIT when the workspace has one number of the carrier; with several it is required.
retry_delay_minutesNoWait before a retry (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / channel_account_id
      Added value: +{
      +  "description": "The phone number the campaign calls from (id from channels.list). OMIT when the workspace has one number of the carrier; with several it is required.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added

TDQS

B3.4/5.0
Behavior1/5

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

The description portrays a side-effecting operation that creates a campaign and immediately places outbound calls to real phone numbers, while annotations declare readOnlyHint=true and idempotentHint=true. Those claims are mutually exclusive: repeated invocation would start additional campaigns and additional live calls. The description's useful details (bounded concurrency, no-answer retries, autonomous dialing) do not cure the conflict.

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 core verb and mechanism are front-loaded in the first clause, and the two short follow-up sentences add constraints without waste. The carrier note is slightly compressed ('twilio/telnyx') but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation tool with no output schema, the description covers what it does and how it behaves but says nothing about what is returned (e.g., a campaign id) or how to track progress afterward. An agent calling this correctly still has to infer the monitoring path from sibling names.

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% and every one of the 11 parameters has an inline description, so the schema already carries the parameter semantics. The description adds no per-parameter meaning (e.g., it never mentions channel_account_id selection rules or defaults), which is acceptable given full coverage but earns only the baseline.

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?

The first sentence gives a specific verb ('Start'), a specific resource ('bulk outbound call campaign'), and the mechanism ('dial a list of phone numbers with a voice agent'). It is immediately distinguishable from the sibling lifecycle tools (campaigns_pause, campaigns_resume, campaigns_cancel, campaigns_list).

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 the applicable channel constraint ('Phone network only (twilio/telnyx)') and removes a would-be prerequisite by saying 'no separate start' is needed. It does not name alternatives or exclusions explicitly (e.g., use campaigns_list to inspect, campaigns_cancel to abort), so guidance is clear but not fully enumerated.

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.