Skip to main content
Glama

Metadata MCP Connector

Remove Offers from Campaign

remove_offers_from_campaign
Destructive

Remove offers. Lead Gen forms OR Landing Pages. from one or more channels in an existing campaign. A launched campaign's X channel (TWITTER) is view-only, so removals there are refused.

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>",
      "channel_offers": "<channel_offers>"
    },
    "name": "remove_offers_from_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesThe unique identifier of the campaign
channel_offersYesMap of channel type to list of offer names (Lead Gen form or Landing Page) to remove. Example: {"FACEBOOK": ["Demo Form"], "GOOGLE_ADS": ["Pricing LP"]}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the safety profile is covered; the description adds real behavioral context beyond that by disclosing that a launched campaign's X (TWITTER) channel is view-only and removals there are refused. It leaves open whether the call is all-or-nothing when one channel in the map fails, which matters for a destructive multi-channel mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but sentence structure is broken: 'Remove offers. Lead Gen forms OR Landing Pages. from one or more channels' reads as three fragments with stray periods, forcing the reader to reassemble the meaning. The useful constraint about TWITTER is at least front-loaded at the end of a compact block.

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?

For a destructive tool with a nested map parameter and no output schema, the description covers the main scope and one failure mode. It does not say whether removals are partial or atomic across channels, what is returned, or whether offers already absent cause an error, leaving meaningful gaps for an agent planning the call.

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%, including an inline example for the channel_offers map, so the baseline is 3. The description adds only the clarification that offers are Lead Gen forms or Landing Pages, which slightly constrains what strings are valid but does not explain key format, channel-name casing, or partial failure per channel.

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 names a specific verb and resource ('Remove offers ... from one or more channels in an existing campaign') and narrows the resource to 'Lead Gen forms OR Landing Pages', which separates it from channel-level or ad-level siblings. It stops short of naming any sibling explicitly, so an agent must infer the boundary with remove_channels_from_campaign and remove_ad_from_campaign.

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?

Usage is implied by the phrase 'in an existing campaign' and by the view-only caveat, which tells the agent one case where the call will fail. There is no explicit guidance on when to choose this over removing channels or ads, and no statement of preconditions such as campaign launch state or required permissions.

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