CallMCP — Phone Call MCP Server

Create Campaign

create_campaign

Destructive

Create an outbound call campaign (cadence + lead batch) and optionally launch it immediately. Launching queues calls for the orchestrator; existing TCPA/consent gating still applies at dial time. Requires admin role on the business.

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

Input Schema

Name	Required	Description
`name`	Yes	Campaign name.
`launch`	No	When true, launch the campaign immediately after creating it.
`agent_id`	No	Agent ID to place the calls. Required when launch is true.
`lead_ids`	No	Lead IDs to enroll in the campaign (optional at create time).
`business_id`	No	Business ID (required only when the token can access multiple businesses).
`description`	No	Optional campaign description.
`cadence_config`	Yes	Cadence configuration. { template: standard\|aggressive\|nurture\|custom, attempts: number }.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`queued`	No
`success`	Yes	Whether the tool completed successfully
`campaign`	No
`launched`	No
`sequence_id`	No
`total_leads`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety bar is lower; the description still adds real value by disclosing the side effect (launching queues calls for the orchestrator), the compliance gate (TCPA/consent applies at dial time) and the admin-role prerequisite. It does not clarify whether a duplicate name creates a second campaign given idempotentHint=false, which would be the remaining gap. No contradiction with annotations.

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?

Three sentences, front-loaded with the capability, then the launch side effect, then the prerequisite. No filler, and each sentence carries distinct information.

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?

The tool has an output schema and full schema coverage, so return values and parameter formats need not be explained; the description covers the side effect, permission requirement and the create/launch coupling. It leaves unaddressed how this relates to the separate launch_call_campaign and pause_call_campaign lifecycle, which would fully orient an agent.

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 coverage is 100%, so every parameter, including the nested cadence_config fields and the enum-like template values, is already documented in the schema; baseline 3 applies. The description adds only the framing that cadence and lead batch are the core inputs, and the schema itself already states agent_id is required when launch is true.

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?

States a specific verb and resource plus the substance of the resource: 'Create an outbound call campaign (cadence + lead batch) and optionally launch it immediately.' The create-vs-launch split is explained, which helps separate it from launch_call_campaign. It stops short of explicitly naming that sibling, so an agent must infer the boundary.

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?

Useful conditions are given: launching is optional at create time, and admin role on the business is required. However, nothing states when to create here versus creating then calling launch_call_campaign, nor any exclusion such as when a campaign should not be created.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CallMCP — Phone Call MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.