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 attaching a shared set

attach_shared_set_to_campaigns

Attach a shared negative keyword list to multiple Google Ads campaigns and preview the changes before applying them.

Instructions

Attach an existing shared set to one or more campaigns — returns a PREVIEW.

Creates CampaignSharedSet linkages so the campaigns inherit the shared set's criteria (e.g. negative keywords). Most commonly used to attach a shared negative keyword list to newly-built campaigns; get_negative_keyword_list_campaigns lists 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": "attach_shared_set_to_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
campaign_idsYesNumeric campaign IDs to attach the set to (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 attach the set to (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. Addedv0.13.2
  3. Removedv0.13.0
  4. First observedv0.9.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true, which alone would leave the agent unsure whether this mutates state. The description resolves that by explaining it returns a PREVIEW with a plan_id and that nothing changes until confirm_and_apply applies it — a two-phase workflow annotations cannot express.

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-loaded with the action and the preview caveat, then the mechanism, use case, and apply step. Efficient overall, though the trailing Google Ads API documentation URL is low-value filler 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?

An output schema exists so return values need no explanation, and the description covers the key workflow context (preview -> confirm_and_apply) that an agent needs to call this correctly. Nothing essential 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 the schema already documents shared_set_id, campaign_ids, and customer_id (including dedup behavior). The description adds conceptual context ('campaigns inherit the shared set's criteria') but no parameter-level detail beyond the schema. 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 ('Attach an existing shared set to one or more campaigns') and immediately scopes it as a preview. It is clearly distinguishable from detach_shared_set_from_campaigns and get_negative_keyword_list_campaigns, both named or implied in siblings.

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?

Gives a concrete primary use case ('attach a shared negative keyword list to newly-built campaigns') and points to get_negative_keyword_list_campaigns for inspecting existing attachments. It does not explicitly state when not to use it (e.g. vs attach_brand_list_to_campaigns), but the context is clear enough to route correctly.

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