Google Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

google ads get simulations

google_ads_get_simulations

Read-onlyIdempotent

Query campaign, ad group, or portfolio bidding simulations to retrieve simulation metadata and projected performance points for planning and forecasting.

Instructions

Read-only planning/forecast query for campaign, ad group, or portfolio bidding simulations. Returns simulation metadata and projected point lists when available, with a metadata fallback.

Input Schema

Name	Required	Description	Default
`level`	No	Simulation resource level to query	campaign
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`adGroupId`	No	Optional ad group ID filter for ad_group simulations
`campaignId`	No	Optional campaign ID filter. Applies directly to campaign simulations and as campaign context for ad group simulations.
`customerId`	Yes	Google Ads customer ID (without dashes, e.g., 1234567890)
`typeFilter`	No	Optional SimulationType enum, e.g. BUDGET, TARGET_CPA, TARGET_ROAS, CPC_BID
`biddingStrategyId`	No	Optional portfolio bidding strategy ID filter for bidding_strategy simulations
`simulationEndDate`	No	Optional maximum simulation end date YYYY-MM-DD
`modificationMethod`	No	Optional SimulationModificationMethod enum, e.g. UNIFORM, SCALING, DEFAULT
`simulationStartDate`	No	Optional minimum simulation start date YYYY-MM-DD

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / adGroupId / $ref
```
Removed value: -"#/properties/campaignId"
```
addedInput schema / properties / adGroupId / pattern
```
Added value: +"^\\d+$"
```
addedInput schema / properties / adGroupId / type
```
Added value: +"string"
```
removedInput schema / properties / biddingStrategyId / $ref
```
Removed value: -"#/properties/campaignId"
```
addedInput schema / properties / biddingStrategyId / pattern
```
Added value: +"^\\d+$"
```
addedInput schema / properties / biddingStrategyId / type
```
Added value: +"string"
```
removedInput schema / properties / modificationMethod / $ref
```
Removed value: -"#/properties/typeFilter"
```
addedInput schema / properties / modificationMethod / pattern
```
Added value: +"^[A-Z0-9_]+$"
```
addedInput schema / properties / modificationMethod / type
```
Added value: +"string"
```
removedInput schema / properties / simulationEndDate / $ref
```
Removed value: -"#/properties/simulationStartDate"
```
addedInput schema / properties / simulationEndDate / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
addedInput schema / properties / simulationEndDate / type
```
Added value: +"string"
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the return behavior ('simulation metadata and projected point lists ... with a metadata fallback'), which is genuinely useful beyond annotations, but does not discuss pagination limits, empty results, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose and scope, with no filler. The only slight inefficiency is that 'read-only' is already covered by annotations, but it is not harmful.

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?

With an output schema, 10 fully documented parameters, and rich annotations, the description supplies the essential framing (what kind of query, which levels, what kind of result). It is complete enough to call correctly, though it could say more about pagination or when simulations are unavailable.

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 description coverage is 100%, so every parameter is already documented in the schema (including enums, patterns, and defaults). The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

The description states a specific verb and resource ('planning/forecast query for ... bidding simulations') and names the three supported levels (campaign, ad group, portfolio bidding). It is distinguishable from siblings like get_bidding_strategies, but does not explicitly contrast with any alternative tool.

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 phrase 'planning/forecast query' implies the use case, and 'read-only' signals safety, but there is no explicit when-to-use/when-not guidance or named alternative. An agent must infer that this is the right tool for simulation data rather than, say, get_bidding_strategies.

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

Deploy Server