Skip to main content
Glama

google_ads_bid_adjustments_update

Update bid modifier on a campaign criterion to adjust bids for specific targeting. Requires campaign ID, criterion ID, and bid modifier (0.1-10.0). Reversible. Returns resource name.

Instructions

Update the bid_modifier of a single campaign_criterion. Returns {resource_name} of the updated criterion. Mutating — FieldMask-based partial update on bid_modifier only; other criterion fields are preserved. Reversible by another call to this tool. bid_modifier must be 0.1-10.0 (0.1 = -90%, 1.0 = neutral, 10.0 = +900%); values outside this range raise ValueError. To toggle a device on/off with bid_modifier 0.0 use google_ads_device_targeting_set instead (this tool rejects 0.0).

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.
criterion_idYesCriterion ID as a numeric string (e.g. '30001'). Obtain via google_ads_bid_adjustments_get or google_ads_device_targeting_get.
bid_modifierYesNew bid modifier (0.1 = -90%, 1.0 = no change, 2.0 = +100%, 10.0 = +900%). Outside 0.1-10.0 raises ValueError server-side.
Behavior4/5

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

Discloses mutating nature, FieldMask-based partial update, and that other fields are preserved. Specifies range constraints (0.1-10.0) and behavior outside range (ValueError). Reversibility stated. No annotations provided, so description carries full burden; slightly lacks permission/authentication details but covers key behavioral aspects.

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?

Three concise sentences covering purpose, behavior, and constraints. No redundant information. Well-structured with clear separation of concerns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema or annotations, description provides return value, usage guidance, parameter semantics, and links to sibling tools. Could mention error handling for non-existent criteria, but overall sufficiently complete for a mutation tool.

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 coverage is 100%, so baseline is 3. Description adds value by explaining bid_modifier values (e.g., 0.1=-90%, 1.0=neutral, 10.0=+900%) and how to obtain campaign_id and criterion_id via other tools, exceeding schema documentation.

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 'Update the bid_modifier of a single campaign_criterion', specifying verb and resource. Distinguishes from sibling google_ads_device_targeting_set by noting that tool handles bid_modifier 0.0 for toggling. Explicit return value {resource_name}.

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 (update bid_modifier) and when not to use (toggle device on/off, directing to google_ads_device_targeting_set). Also mentions reversibility via another call, providing clear context for decision-making.

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