Skip to main content
Glama

Metadata MCP Connector

Remove Channels from Campaign

remove_channels_from_campaign
Destructive

Disable one or more entire channels from an existing campaign.

            Use this tool when the goal is to turn off a whole channel (e.g. stop running
            ads on FACEBOOK entirely). To remove a specific audience from a channel instead,
            use remove_audiences_from_campaign.

            KEYWORDS: remove, delete, disable, channel, campaign

            WHEN TO USE:
            - Disable/remove an entire channel from a campaign (e.g. remove FACEBOOK or GOOGLE_ADS)
            - Multiple channels can be disabled in a single call
            - Returns the campaign state before and after the change

            RESPONSE:
            - Returns the refreshed campaign state plus a removal_results list with one
              entry per requested removal recording its success or error. ALWAYS check
              removal_results — a partial failure (e.g. one of two names not found) still
              returns normally, so report only what actually came back successful.

            REQUIRED PARAMETERS:
            - campaign_id: Campaign ID (numeric identifier)
            - channels: Array of channel types to disable

            CHANNEL TYPES: FACEBOOK, INSTAGRAM, GOOGLE_ADS, LINKEDIN, MICROSOFT_ADS, REDDIT

            EXAMPLES:

            Disable a single channel:
            remove_channels_from_campaign({
                "campaign_id": 12345,
                "channels": ["FACEBOOK"]
            })

            Disable multiple channels at once:
            remove_channels_from_campaign({
                "campaign_id": 12345,
                "channels": ["FACEBOOK", "GOOGLE_ADS", "INSTAGRAM"]
            })

            INTEGRATION WITH OTHER TOOLS:
            - Use search_campaigns_by_names to find the campaign ID
            - Use get_campaign_by_wizard_id to inspect active channels before removal
            - Use remove_audiences_from_campaign to remove a specific audience from a channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsYesList of channels to disable from the campaign. Example: ["FACEBOOK", "GOOGLE_ADS"]
campaign_idYesThe unique identifier of the campaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already set destructiveHint=true and readOnlyHint=false, but the description adds valuable behavioral detail: it notes that the response includes the campaign state before and after the change, and warns about partial failures (removal_results must be checked because a failed name still returns normally). This goes beyond the annotations and clarifies the operational behavior, though it could mention idempotency or side effects explicitly.

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 structured with clear sections (purpose, WHEN TO USE, RESPONSE, REQUIRED PARAMETERS, CHANNEL TYPES, EXAMPLES, INTEGRATION). It is front-loaded with the core purpose and each section earns its place. No fluff or redundancy; the examples and notes are directly useful.

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 tool with only two parameters and no output schema, the description is remarkably complete. It explains the response structure, partial-failure handling, valid channel enum values, and how to find campaign IDs via search_campaigns_by_names or inspect channels via get_campaign_by_wizard_id. An agent has everything needed to call it correctly and interpret results.

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 input schema already covers both parameters with descriptions and an enum for channels. The description reinforces the meaning by explaining that 'entire channels' are disabled and provides concrete examples of valid channel values. It also clarifies the difference between channel removal and audience removal, which adds semantic depth beyond the raw schema.

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 precise verb and resource: 'Disable one or more entire channels from an existing campaign.' It immediately distinguishes itself from the sibling remove_audiences_from_campaign by clarifying the scope (entire channel vs. specific audience). This leaves no ambiguity about what the tool does and how it differs from alternatives.

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 description explicitly states when to use this tool: 'Use this tool when the goal is to turn off a whole channel...' and contrasts it with remove_audiences_from_campaign. It also includes a 'WHEN TO USE' section and an 'INTEGRATION WITH OTHER TOOLS' section that names specific alternatives and companion tools, providing clear routing guidance.

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