Skip to main content
Glama

List voice campaigns

list_voice_campaigns
Read-onlyIdempotent

List the voice campaigns of this account, newest first, 25 per page (meta.total_count is the total). Each has its status (draft, scheduled, running, paused, completed, cancelled, failed), whether it is outbound (the dialer calls contacts) or inbound (agents answer the PBX queues in inbound_queue_ids), its dialer mode and the progress counters. Contacts and their phone numbers are not included. Archived campaigns (archived_at set) and test campaigns (test true) are left out unless asked (archived, include_test); q searches the title, from/to the creation date. A campaign that is a batch and sweep of a program carries program_id, batch_label and sweep_number (filter by program_id or batch_label).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_voice_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPart of the campaign title.
toNoCreated at or before: YYYY-MM-DD covers that whole day; an ISO 8601 timestamp is used as is.
fromNoCreated at or after: YYYY-MM-DD (from the start of that day) or an ISO 8601 timestamp, used as is.
pageNo
fieldsNoOptional: return only these fields of each record.
archivedNofalse (default) lists unarchived campaigns only, true archived ones only, all both.
program_idNoOnly the campaigns of this program (id from list_voice_campaign_programs).
batch_labelNoOnly the campaigns of this batch.
include_testNoInclude test campaigns (left out by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "false (default) lists unarchived campaigns only, true archived ones only, all both.",
      +  "enum": [
      +    "false",
      +    "true",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / batch_label
      Added value: +{
      +  "description": "Only the campaigns of this batch.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "title",
      -  "description",
      -  "status",
      -  "handler_type",
      -  "direction",
      -  "dialer_mode",
      -  "executor_type",
      -  "inbound_queue_ids",
      -  "total_contacts",
      -  "contacts_pending",
      -  "contacts_called",
      -  "contacts_answered",
      -  "contacts_completed",
      -  "contacts_failed",
      -  "scheduled_at",
      -  "started_at",
      -  "completed_at",
      -  "created_at"
      -]New value: +[
      +  "id",
      +  "title",
      +  "description",
      +  "status",
      +  "handler_type",
      +  "direction",
      +  "dialer_mode",
      +  "executor_type",
      +  "agent_user_ids",
      +  "inbound_queue_ids",
      +  "total_contacts",
      +  "contacts_pending",
      +  "contacts_called",
      +  "contacts_answered",
      +  "contacts_completed",
      +  "contacts_failed",
      +  "scheduled_at",
      +  "ends_at",
      +  "started_at",
      +  "completed_at",
      +  "created_at",
      +  "voice_line_id",
      +  "ai_settings",
      +  "archived_at",
      +  "test",
      +  "program_id",
      +  "batch_label",
      +  "sweep_number",
      +  "validation_summary"
      +]
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Created at or after: YYYY-MM-DD (from the start of that day) or an ISO 8601 timestamp, used as is.",
      +  "type": "string"
      +}
    • addedInput schema / properties / include_test
      Added value: +{
      +  "description": "Include test campaigns (left out by default).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / program_id
      Added value: +{
      +  "description": "Only the campaigns of this program (id from list_voice_campaign_programs).",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Part of the campaign title.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Created at or before: YYYY-MM-DD covers that whole day; an ISO 8601 timestamp is used as is.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses pagination (25 per page), sort order (newest first), where the total lives (meta.total_count), and what is deliberately absent from records (contacts and phone numbers). It also spells out default exclusion of archived_at-set and test=true campaigns, which is behavior an agent cannot infer from the annotations or schema defaults alone.

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?

Content is front-loaded with the core operation, ordering, and page size before moving to record contents, defaults, and filters. The single dense paragraph runs long and mixes return-shape, defaults, and filtering into one block, which costs a little scannability but wastes no sentences.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does: per-campaign status enumeration, inbound/outbound direction, dialer mode, progress counters, and meta.total_count. It also covers the program/batch linkage fields and the filters that address them, leaving no obvious gap for a 9-parameter list tool.

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 89%, so nearly every parameter is already documented in the input schema, including q, from/to formats, archived enum values, and program_id/batch_label. The description largely restates those semantics rather than adding new meaning, so the baseline of 3 applies.

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 opens with a specific verb and resource ('List the voice campaigns of this account') and immediately constrains scope with ordering and page size. It clearly separates voice campaigns from the generic list_campaigns / list_whatsapp_campaigns siblings by naming the resource explicitly, but never states the alternative channel tools outright.

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 explains default behavior (archived and test campaigns are left out 'unless asked') and how to override that via archived/include_test, plus which parameter searches what (q on title, from/to on creation date). It stops short of saying when to prefer get_voice_campaign or get_voice_campaign_report over this list view.

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