Skip to main content
Glama
Sign In
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft detaching a shared set

detach_shared_set_from_campaigns

Removes shared set attachments from one or more campaigns so they stop inheriting its criteria. Returns a preview; nothing changes until it is confirmed.

Instructions

Detach a shared set from one or more campaigns — returns a PREVIEW.

Removes CampaignSharedSet linkages so the campaigns no longer inherit the shared set's criteria. The shared set itself is unchanged; only the per-campaign attachment is removed. get_negative_keyword_list_campaigns lists the existing attachments. Returns a preview with a plan_id; nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": {
      "shared_set_id": "<shared_set_id>",
      "campaign_ids": "<campaign_ids>"
    },
    "name": "detach_shared_set_from_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
campaign_idsYesNumeric campaign IDs to detach the set from (at least one). Blank entries are dropped and duplicates collapsed.
shared_set_idYesNumeric ID of the shared set (from get_negative_keyword_lists).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / campaign_ids / description
      Added value: +"Numeric campaign IDs to detach the set from (at least one).\nBlank entries are dropped and duplicates collapsed."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / shared_set_id / description
      Added value: +"Numeric ID of the shared set (from\nget_negative_keyword_lists)."
  2. First observedv0.9.0

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description adds substantial non-obvious context: it is a draft/preview that changes nothing, returns a plan_id, leaves the shared set itself intact, and removes only per-campaign linkages. This clarifies why a 'detach' is non-destructive, which the annotations alone do not explain.

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?

Front-loads the essential scope and PREVIEW behavior in the first line, followed by supporting detail. Well-organized, though the trailing Google Ads API URL is boilerplate that doesn't earn much space.

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 draft-mutation tool with an output schema and annotations, this description is complete: it covers the linkage semantics, the preview/plan_id lifecycle, the confirm step, and the discovery sibling. Nothing an agent needs to call it correctly is missing.

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%, so all three parameters are already documented in the schema. The description adds only that the detachment targets 'one or more campaigns,' which is marginally beyond what the schema states. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Detach a shared set from one or more campaigns') and immediately flags that it returns a PREVIEW, which distinguishes it from the actual-apply sibling confirm_and_apply. An agent can tell exactly what the tool does without opening the schema.

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?

Provides the workflow: get_negative_keyword_list_campaigns lists existing attachments (discovery), this tool produces a plan_id preview, and confirm_and_apply executes it. Clear context for when to use it, though it does not state explicit when-not-to-use conditions.

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

Deploy Server

Other Tools