Skip to main content
Glama

google_ads_bid_adjustments_get

List every campaign criterion row with a non-null bid modifier for a Google Ads campaign. Returns criterion ID, type (DEVICE, LOCATION, AD_SCHEDULE), bid modifier, and device type. Requires campaign ID.

Instructions

List every campaign_criterion row that has a non-null bid_modifier on a Google Ads campaign. Returns [{criterion_id, type (CriterionType enum string, e.g. 'DEVICE', 'LOCATION', 'AD_SCHEDULE'), bid_modifier (float), device_type ('DESKTOP'|'MOBILE'|'TABLET' for DEVICE criteria; 'UNKNOWN()' for non-DEVICE rows such as LOCATION or AD_SCHEDULE, where n is the raw device-type enum ordinal — never null)}]. Read-only. For the device-summary view (all three devices, even implicit ones) use google_ads_device_targeting_get. For location-only use google_ads_location_targeting_list.

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.
Behavior4/5

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

Declares read-only, details return format including edge cases for device_type, but does not mention pagination or authentication needs. Without annotations, this is strong but not exhaustive.

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?

Two concise sentences with front-loaded purpose, no wasted words.

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?

No output schema, but description provides complete return structure. Covers purpose, usage, behavior, and alternatives. Adequate for a list tool.

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 covers both parameters fully (100% coverage). Description adds minimal extra beyond schema (campaign_id source mentioned, but already in schema). Baseline 3 applies.

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?

Description clearly states the tool lists campaign_criterion rows with non-null bid_modifier, specifies returned fields, and distinguishes from sibling tools (google_ads_device_targeting_get, google_ads_location_targeting_list).

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 tells when to use (get non-null bid adjustments) and provides alternatives for device-summary and location-only use cases, guiding agent to appropriate tools.

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