Metadata MCP Connector

Manage Campaign

manage_campaign

Destructive

Manage a campaign by pausing or restarting it.

            KEYWORDS: pause, stop, restart, resume, unpause, campaign, control, manage, halt

            WHEN TO USE:
            - User asks to "pause campaign X"
            - User wants to "stop campaign Y"
            - User requests to "restart campaign Z"
            - User wants to "resume campaign A"
            - User asks to "unpause campaign B"

            ACTIONS:
            - pause: Temporarily pause an active campaign to stop ad serving and budget spend
            - restart: Resume a paused campaign to continue ad serving and budget spend

            REQUIRED PARAMETERS:
            - campaign_id: The unique identifier of the campaign to manage (integer, required)
            - action: The action to perform - "pause" or "restart" (string, required)

            CAMPAIGN ID SOURCES:
            Campaign IDs can be obtained from:
            - search_campaigns_by_names tool
            - create_campaign tool response
            - Campaign management interface URLs

            IMPORTANT VALIDATION REQUIREMENTS:
            - **CRITICAL**: You can ONLY pause campaigns that are currently "Active"
            - **CRITICAL**: You can ONLY restart campaigns that are currently "Paused"
            - Before attempting to pause or restart, use search_campaigns_by_names to verify the current campaign status

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	The action to perform: 'pause' to stop the campaign, 'restart' to resume it
`campaign_id`	Yes	The unique identifier of the campaign to manage

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description explains that pausing stops ad serving and budget spend while restart resumes them. It also discloses the critical state validation requirement, giving the agent actionable behavioral context without contradicting any annotation.

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 well-organized with clear sections and a front-loaded summary. Some redundancy exists—KEYWORDS overlaps WHEN TO USE and REQUIRED PARAMETERS restates the schema—but the structure remains scannable and useful for an agent.

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?

For a two-parameter mutation tool with no output schema, the description covers purpose, when to use, action semantics, parameter sources, and validation preconditions. Nothing material is missing for an agent to invoke the tool correctly.

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

Parameters4/5

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

The schema already covers both parameters with descriptions and an enum, so the baseline is 3. The description adds meaning by explaining the operational effect of each action and listing concrete sources for campaign_id, though some of this repeats what the schema already says.

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?

The description opens with a specific action-resource pairing: 'Manage a campaign by pausing or restarting it.' It then enumerates exactly two supported actions, pause and restart, which distinguishes it from sibling campaign tools like create_campaign, launch_campaign, and duplicate_campaign.

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

Usage Guidelines5/5

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

The 'WHEN TO USE' section lists concrete user intents: pause, stop, restart, resume, and unpause. It also gives hard preconditions—only Active campaigns can be paused and only Paused campaigns can be restarted—and instructs the agent to verify status with search_campaigns_by_names before acting.

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

All Metadata MCP Connector 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.

Resources

Need Help?