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.

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>",
      "channels": "<channels>"
    },
    "name": "remove_channels_from_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsYesList of channels to disable from the campaign (TWITTER is X). Example: ["FACEBOOK", "GOOGLE_ADS"]
campaign_idYesThe unique identifier of the campaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / channels / description
      Previous value: -"List of channels to disable from the campaign. Example: [\"FACEBOOK\", \"GOOGLE_ADS\"]"New value: +"List of channels to disable from the campaign (TWITTER is X). Example: [\"FACEBOOK\", \"GOOGLE_ADS\"]"
    • changedInput schema / properties / channels / items / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "GOOGLE_ADS",
      -  "LINKEDIN",
      -  "MICROSOFT_ADS",
      -  "REDDIT"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "GOOGLE_ADS",
      +  "LINKEDIN",
      +  "MICROSOFT_ADS",
      +  "REDDIT",
      +  "TWITTER"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds meaningful context by framing the operation as 'disabling' whole channels rather than deleting individual entities, which tells the agent the change is channel-wide. It does not say whether disabling is reversible, what happens to existing ads or keywords under those channels, or whether the campaign must be paused first.

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?

A single front-loaded sentence with no filler. Every word, particularly 'entire' and 'existing', carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two fully documented parameters, no output schema, and complete annotations, the definition is minimally sufficient to invoke the tool correctly. It is thin on operational context, such as preconditions on campaign state and what the caller gets back after the channels are disabled.

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 description coverage is 100%, and the schema already documents both campaign_id and the channels list, including an example and the TWITTER-is-X note. The description adds nothing beyond that, so the baseline of 3 applies.

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 gives a specific verb-plus-resource pair: 'Disable one or more entire channels from an existing campaign.' The qualifier 'entire channels' separates it from granular siblings such as remove_ad_from_campaign or remove_keywords_from_campaign. It stops short of naming an alternative, but the scope is unambiguous.

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

Usage Guidelines2/5

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

The only guidance is the implicit precondition that the campaign must already exist. Nothing states when to use this versus remove_ad_from_campaign or remove_keywords_from_campaign, and nothing describes exclusions or side effects that would steer selection. An agent must infer routing from the tool name alone.

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