Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_device_targeting_set

Toggle device delivery on a Google Ads campaign: set enabled devices to bid_modifier=1.0, disabled to 0.0, updating or creating criteria individually.

Instructions

Toggle device delivery on a Google Ads campaign by setting bid_modifier=1.0 on enabled devices and 0.0 on disabled ones. Iterates all three devices individually so one failure does not abort the others. Returns {message, enabled_devices (sorted list), disabled_devices (sorted list), updated (list of resource_names that succeeded), errors (list of '(): ' strings, or null)}. Mutating — existing device criteria are UPDATE-ed, missing ones are CREATE-ed. Reversible only by calling this tool again with a different enabled_devices. enabled_devices must be non-empty (passing an empty array raises ValueError). For fine-grained non-zero bid modifiers use google_ads_bid_adjustments_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
enabled_devicesYesDevices that should continue serving (bid_modifier=1.0). Devices not in this list have bid_modifier set to 0.0 (delivery off). At least one device must be enabled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.10.11
  4. Removedv0.10.9
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility and delivers richly: it discloses partial-failure handling ('Iterates all three devices individually so one failure does not abort the others'), mutation semantics ('existing device criteria are UPDATE-ed, missing ones are CREATE-ed'), reversibility, the empty-array ValueError, and the exact return shape. There is no annotation to contradict, and the behavioral detail is exemplary.

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 dense but every sentence earns its place: purpose, iteration behavior, return structure, mutation semantics, reversibility, constraint, and alternative. It is well-structured and front-loaded with the core action, followed by essential operational details and the sibling pointer.

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?

Given no output schema and no annotations, the description compensates fully: it specifies the return object structure with field types, clearly marks the operation as mutating, describes failure isolation, and provides the alternative tool. It even covers edge-case behavior (empty array raises ValueError). Nothing an agent needs to call this 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 the schema already documents all parameters. The description adds context about bid_modifier values and the update/create behavior, but these are behavioral traits rather than parameter-level semantics. It does not expand on campaign_id, customer_id, or reason beyond the schema, making the baseline 3 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?

The description opens with a specific verb and resource: 'Toggle device delivery on a Google Ads campaign by setting bid_modifier=1.0 on enabled devices and 0.0 on disabled ones.' It clearly distinguishes itself from sibling tools by naming google_ads_bid_adjustments_update as the alternative for fine-grained modifiers, and the read-only sibling google_ads_device_targeting_get is naturally excluded by the mutating semantics.

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 the core use case (toggle device delivery on/off) and directly names the alternative: 'For fine-grained non-zero bid modifiers use google_ads_bid_adjustments_update.' It also gives practical guidance: 'Reversible only by calling this tool again with a different enabled_devices' and notes the non-empty constraint, which helps the agent decide when and how to invoke it.

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