Skip to main content
Glama

Update voice campaign

update_voice_campaign
DestructiveIdempotent

Change the settings of a voice campaign: a DRAFT takes any of them; a RUNNING or PAUSED one only its title, description, calling window, timezone, end date (ends_at), retry delay, retry after voicemail, concurrency and attempts (attempts can only go up). A SCHEDULED one takes everything except its audience. Send only what changes. It never sets consent and places no call; its contacts change with add_voice_campaign_contacts and remove_voice_campaign_contacts.

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>"
    },
    "name": "update_voice_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
ends_atNoWhen the campaign ends, in the future and after scheduled_at: YYYY-MM-DDTHH:MM in the campaign timezone, or with an offset. Past it the campaign completes, whatever is left to call. An empty string clears it.
audienceNoWith audience_type label: {label_ids: [ids]}; with segment: {custom_filter_id: id}. The contacts are taken when the campaign launches.
timezoneNoIANA name, for example America/Bogota.
ai_settingsNoWhat the AI agent does in this campaign: opening (text per locale es/en), first_speaker (agent or caller), dispositions, extraction_fields, voicemail, hot_lead, ringing_seconds (15 to 60), variable_map. Read get_voice_campaign for the shape in use.
campaign_idYesCampaign id as returned by list_voice_campaigns.
descriptionNo
dialer_modeNoHow fast contacts are dialed (progressive by default); power currently places one call per available agent.
max_attemptsNoCalls to one contact before giving up.
scheduled_atNoWhen to start, in the future: YYYY-MM-DDTHH:MM in the campaign timezone, or with an offset. Launching a campaign that has one schedules it instead of starting it.
audience_typeNoOnly with audience, instead of contact_rows and contact_ids.
voice_line_idNoThe AI phone line that calls (its agent talks, its number shows).
calling_windowNoThe hours and days the campaign may call, in its timezone.
retry_delay_minsNoMinutes before the next attempt.
retry_after_voicemailNoCall again after a voicemail (true by default). False ends the contact on a detected voicemail.
target_concurrency_limitNoCalls at the same time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ends_at
      Added value: +{
      +  "description": "When the campaign ends, in the future and after scheduled_at: YYYY-MM-DDTHH:MM in the campaign timezone, or with an offset. Past it the campaign completes, whatever is left to call. An empty string clears it.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / dialer_mode / description
      Previous value: -"How fast contacts are dialed (progressive by default)."New value: +"How fast contacts are dialed (progressive by default); power currently places one call per available agent."
    • addedInput schema / properties / retry_after_voicemail
      Added value: +{
      +  "description": "Call again after a voicemail (true by default). False ends the contact on a detected voicemail.",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses state-based field restrictions, that attempts can only increase, that only changed fields should be sent, and that the tool never sets consent or places a call. These are important behavioral details for a complex update operation.

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 dense but well structured, front-loading the core action and then listing state-specific constraints. The partial-update instruction and sibling routing are concise and earn their place.

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 16-parameter nested mutation tool with no output schema, the description covers the critical calling semantics, status restrictions, and contact-handling boundaries. It does not describe the response or failure behavior, which leaves a modest completeness gap.

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 description coverage is already high at 88%, so the baseline is 3. The description adds cross-parameter meaning beyond the schema: different campaign statuses permit different parameter subsets, attempts are monotonic, and only changed fields should be included.

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 description states a specific verb and resource: 'Change the settings of a voice campaign.' It also distinguishes this tool from contact-mutating siblings by explicitly saying contacts are changed with add_voice_campaign_contacts and remove_voice_campaign_contacts.

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

Usage Guidelines5/5

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

It gives explicit state-dependent rules: a DRAFT accepts any setting, RUNNING or PAUSED accepts only a listed subset, and SCHEDULED accepts everything except audience. It also says to send only what changes and routes contact changes to the correct siblings.

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