Skip to main content
Glama

Import VOIP Campaign Targets

import_voip_campaign_targets
Destructive

[write] Adds people to a campaign (voip_campaign_id or voip_campaign_uuid) that has not ended, from ONE of: targets (at most 500 at a time; each is {phone, name, vars: {column: value}} or just a phone number) or a saved list (voip_list_id or voip_list_uuid; see list_voip_lists; all its people). Numbers are normalized with the campaign's calling code; duplicates and invalid numbers are counted, not added; numbers on the do-not-call list are recorded as skipped and never called.

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

Input Schema

NameRequiredDescriptionDefault
targetsNo
voip_list_idNo
voip_list_uuidNo
voip_campaign_idNo
voip_campaign_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / targets / anyOf
      Added value: +[
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / targets / default
      Added value: +null
    • removedInput schema / properties / targets / items
      Removed value: -{}
    • removedInput schema / properties / targets / type
      Removed value: -"array"
    • addedInput schema / properties / voip_list_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Voip List Id"
      +}
    • addedInput schema / properties / voip_list_uuid
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Voip List Uuid"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "targets"
      -]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already flag write, destructive, open-world, and non-idempotent behavior, while the description adds concrete consequences: numbers are normalized with the campaign calling code, duplicates and invalid numbers are counted but not added, and do-not-call numbers are skipped and never called. It also adds the 500-target limit and campaign-ended prerequisite, providing substantial context beyond structured fields.

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 description is a single dense paragraph front-loaded with '[write]' and the key source/campaign identifiers. The parenthetical details are useful, but the density makes it slightly harder to scan than an ideal definition.

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?

It covers the complex write operation's input modes, limits, normalization, duplicate/invalid handling, and do-not-call behavior. It does not describe response counts despite there being no output schema, and it does not address required permissions, but it is otherwise sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five optional parameters, but the description explains the targets payload shape and 500 cap, saved list id/uuid, campaign id/uuid, and the one-of source/campaign selection. This compensates strongly for the schema gap, with only minor ambiguity around id-vs-uuid precedence.

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?

States a specific action, 'Adds people to a campaign', and identifies the campaign by id or uuid while restricting the source to targets or a saved list. This clearly distinguishes it from sibling list-membership tools and tells an agent exactly what resource is being mutated.

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 that the campaign must not have ended and that the source must be exactly one of targets or a saved list, and it points to list_voip_lists for saved lists. It does not explicitly compare against add_voip_list_members or state when not to use this tool, so it falls short of full alternative routing.

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.