Skip to main content
Glama

Get voice campaign

get_voice_campaign
Read-onlyIdempotent

Get one voice campaign: status, direction, dialer mode, queues (inbound), schedule and progress counters. An AI voice campaign (handler_type voice_ai) names its AI phone line and its settings: the opening, the dispositions the AI agent records, the facts it collects, the voicemail behaviour and the hot-lead route.

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": "get_voice_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.
campaign_idYesCampaign id as returned by list_voice_campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered; the description earns credit by disclosing the shape of the returned payload (queues for inbound, schedule, progress counters) in the absence of an output schema. It could add more by noting behavior for archived or missing campaigns, so it is not a 5.

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?

Two sentences, with the core purpose front-loaded before entity detail. The second sentence is a dense list of AI settings subfields that is informative but slightly overstuffed, keeping it from a 5.

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 two-parameter read tool with full annotation coverage and no output schema, the description supplies enough about the returned content for an agent to decide to call it. The main residual gap is that it doesn't clarify the relationship to get_voice_campaign_report or the effect of the fields projection on the payload.

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?

With 100% schema description coverage on both parameters, the schema already explains campaign_id (as returned by list_voice_campaigns) and the fields projection. The description adds no syntax or format detail beyond that, so the baseline 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 ('Get one voice campaign') and enumerates the returned facets: status, direction, dialer mode, queues, schedule and progress counters. The second sentence adds entity-specific scope by explaining what an AI voice campaign contains. It stops short of naming how it differs from the closest sibling, get_voice_campaign_report, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

'Get one voice campaign' implies retrieval of a single record by id, which implicitly contrasts with list_voice_campaigns, but the description never says when to reach for this versus the report or list variants. There is no guidance on error conditions for an unknown id or on using the fields parameter to trim the payload.

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