Skip to main content
Glama

google_ads_device_targeting_set

Toggle device delivery for a Google Ads campaign by enabling or disabling mobile, desktop, and tablet devices using bid modifiers.

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
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.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
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.
Behavior5/5

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

No annotations provided, but the description fully covers behavioral traits: mutates by updating existing or creating missing criteria, is reversible only by calling again, and explains the return format including success and error details. Also notes that one failure does not abort others.

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?

Every sentence adds value; the description is front-loaded with the core action and includes necessary details without being verbose. Well-structured and easy to scan.

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, the description adequately explains the return structure, mutation behavior, reversibility, and error handling. It also provides cross-references to sibling tools for further actions, making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters, so baseline is 3. The description adds value by explaining the fallback for customer_id, how to obtain campaign_id, and the effect of enabled_devices on bid modifiers. However, it does not provide significant additional detail beyond the schema descriptions.

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?

Clearly states the tool's purpose: toggling device delivery on a campaign by setting bid modifiers. It distinguishes itself from a sibling tool (google_ads_bid_adjustments_update) for fine-grained bid adjustments.

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?

Explicitly explains when to use the tool (toggle device delivery) and when not to (use google_ads_bid_adjustments_update for non-zero bid modifiers). Also notes the non-empty constraint on enabled_devices and the iterative processing behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server