AdsAgent — Google Ads MCP

google_ads_campaign_create_prepare

Prepare creating a paused campaign and budget. A SEARCH campaign requires location_ids and language_ids; without them the answer is needs_input, never a worldwide campaign.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`roas`	No
`strategy`	No
`customer_id`	Yes	10-digit Google Ads customer id.
`channel_type`	Yes
`language_ids`	No	language_constant ids. Required; there is no implicit all-languages default.
`location_ids`	No	geo_target_constant ids (country, region or city) to target. Required; resolve names with google_ads_geo_targets_suggest.
`amount_micros`	No
`budget_micros`	Yes
`geo_target_type`	No	Defaults to PRESENCE (only people in the location).
`targeting_source`	No	Where the targeting came from; shown in the approval summary. Defaults to user.
`connection_context`	No
`excluded_location_ids`	No	geo_target_constant ids to exclude.
`contains_eu_political_advertising`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 16, 2026

addedInput schema / properties / excluded_location_ids

Added value: +{
+  "description": "geo_target_constant ids to exclude.",
+  "items": {
+    "pattern": "^[1-9][0-9]*$",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / geo_target_type

Added value: +{
+  "description": "Defaults to PRESENCE (only people in the location).",
+  "enum": [
+    "PRESENCE",
+    "PRESENCE_OR_INTEREST"
+  ]
+}

addedInput schema / properties / language_ids

Added value: +{
+  "description": "language_constant ids. Required; there is no implicit all-languages default.",
+  "items": {
+    "pattern": "^[1-9][0-9]*$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / location_ids

Added value: +{
+  "description": "geo_target_constant ids (country, region or city) to target. Required; resolve names with google_ads_geo_targets_suggest.",
+  "items": {
+    "pattern": "^[1-9][0-9]*$",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / targeting_source

Added value: +{
+  "description": "Where the targeting came from; shown in the approval summary. Defaults to user.",
+  "enum": [
+    "user",
+    "template",
+    "source_campaign"
+  ]
+}

Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / contains_eu_political_advertising

Added value: +{
+  "enum": [
+    "CONTAINS_EU_POLITICAL_ADVERTISING",
+    "DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING"
+  ]
+}

changedInput schema / required

Previous value: -[
-  "customer_id",
-  "name",
-  "channel_type",
-  "budget_micros"
-]New value: +[
+  "customer_id",
+  "name",
+  "channel_type",
+  "budget_micros",
+  "contains_eu_political_advertising"
+]

First observedSep 16, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: the campaign is created PAUSED, and the tool returns needs_input rather than silently defaulting to a worldwide campaign. With destructiveHint=false and readOnlyHint=false already covered by annotations, these extra disclosures are meaningful context about what the prepare step does and refuses to do.

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 sentences, zero filler, and the most important constraint (SEARCH needs targeting, never worldwide) is front-loaded after the core purpose. Every clause earns its place.

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

Completeness3/5

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

For a 14-parameter, 5-required creation-prepare tool with no output schema, the description covers the critical gotcha but omits budget/name/channel essentials and what the prepare step returns (an approval plan). Adequate but with clear gaps for something this complex.

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?

With only 43% schema description coverage across 14 params, the description compensates partially by reinforcing the location_ids/language_ids requirement, but it says nothing about roas, strategy, channel_type, geo_target_type, targeting_source, excluded_location_ids, or the required contains_eu_political_advertising flag. Baseline 3 given the schema does describe the two most nuanced params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (prepare/create) and resources (paused campaign + budget), which cleanly distinguishes it from the sibling google_ads_campaign_create_confirm that executes. It doesn't name that sibling explicitly, but the prepare/confirm pairing is signaled by the name and description.

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?

Gives one concrete conditional rule (SEARCH campaigns require location_ids and language_ids, else needs_input), which is genuinely useful usage guidance. However, it never states when to call this versus campaign_create_confirm, or what the prerequisite flow is, so guidance is implied rather than explicit.

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

All AdsAgent — Google Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?