OutreachPilot MCP Server

get_campaign

Retrieve full campaign details including configuration, steps, and audience statistics. Get a complete overview to review and manage your outreach campaigns.

Instructions

Get full details of a single campaign including its config, steps, and audience statistics.

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_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes	ID of the campaign to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It only lists returned data and does not state whether the operation is read-only, requires special permissions, or has other side effects, leaving safety assumptions unconfirmed.

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 a single, clear sentence that front-loads the verb and resource, with no unnecessary words or repetition. It is appropriately sized for the tool's simplicity.

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 simple one-parameter get tool with no output schema, the description provides a reasonable overview of return contents (config, steps, audience statistics). It could be more complete by describing the return format, but it sufficiently covers the tool's purpose and scope.

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?

The schema provides a complete description (100% coverage) for the single parameter campaign_id, so the baseline is 3. The description does not add additional semantic detail beyond what the schema already specifies.

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 clearly states the tool retrieves a single campaign's full details, including config, steps, and audience statistics. This distinguishes it from siblings like get_campaign_status, but does not explicitly name alternatives.

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?

The description implies usage when full campaign details are needed, contrasting with list_campaigns or get_campaign_status. However, it lacks explicit when-not-to-use guidance or named alternatives.

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