Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_batch_update_bids

Update CPC bids for multiple keywords or ad groups in a single batch operation using JSON input.

Instructions

Update CPC bids for multiple keywords or ad groups in a single batch operation.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) entity_type: Type of entity (keyword or ad_group) bid_updates_json: JSON array of bid update configurations

Bid Update Schema (Keywords):

[
  {
    "ad_group_id": "12345678",
    "criterion_id": "87654321",
    "cpc_bid": 2.50
  }
]

Bid Update Schema (Ad Groups):

[
  {
    "ad_group_id": "12345678",
    "cpc_bid": 2.50
  }
]

Returns: Batch operation result with success/failure details

Example: google_ads_batch_update_bids( customer_id="1234567890", entity_type="keyword", bid_updates_json='[{"ad_group_id": "12345678", "criterion_id": "87654321", "cpc_bid": 2.50}]' )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
entity_typeYes
bid_updates_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions batch operation and returns 'success/failure details', but lacks details on atomicity, limits, idempotency, or error handling beyond vague result.

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?

Well-structured with Args, Schemas, Returns, Example sections. Every sentence is informative; no fluff. Purpose is front-loaded.

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 output schema exists, description doesn't need full return details. Parameters are well-explained. Could be improved by adding batch size limits or atomicity behavior, but overall sufficient.

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

Parameters5/5

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

Schema coverage is 0%, but description fully compensates by explaining each parameter: customer_id format, entity_type values, bid_updates_json with complete JSON schemas for both entity types and an example.

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 updates CPC bids for multiple keywords or ad groups in a batch, with specific verb and resource. It differentiates from siblings like single-update tools by emphasizing 'batch operation'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for batch updates but does not explicitly contrast with single-update tools or provide when-not-to-use guidance. No alternatives are mentioned.

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/johnoconnor0/google-ads-mcp'

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