Skip to main content
Glama

google_ads_device_targeting_set

Toggle device delivery on Google Ads campaigns by setting bid modifiers to enable or disable MOBILE, DESKTOP, or TABLET devices, updating or creating criteria as needed.

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?

Discloses mutating behavior (UPDATE or CREATE), iteration over devices for partial failures, return format with errors, and reversible nature. No annotations provided; description fully covers behavioral traits.

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?

Concise single paragraph with all essential information front-loaded. Every sentence adds value without redundancy.

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?

Complete given no output schema: explains return structure, error handling, and sibling tool. Covers all necessary aspects for agent to use correctly.

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?

Input schema has 100% coverage with descriptions. The description adds operational context for enabled_devices (bid_modifier logic) but does not significantly enhance other parameters beyond schema.

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 clearly states the tool's purpose: toggling device delivery by setting bid modifiers to 1.0 or 0.0. It distinguishes from the sibling tool google_ads_bid_adjustments_update for fine-grained 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 states when to use (toggle device delivery), when not to use (refer to bid_adjustments_update), and prerequisites (enabled_devices must be non-empty). Also notes reversibility by calling again.

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