Google

Google Ads

Curated anchor platform in paid search and performance media with material relevance to the Marcom operating stack and a first-party developer surface.

Advertising & media buyingSystem of engagementBYO-UI-ready platform

Representative source ↗Product site ↗

System roleSystem of engagement

Access maturityBYO-UI-ready platform

Agent postureFirst-party provider

Reference updatedJun 29, 2026

BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Strictly read-only: account discovery, GAQL search/reporting, resource metadata

02 · Data you can retrieve

Strictly read-only: account discovery, GAQL search/reporting, resource metadata

03 · Actions and write paths

No Google Ads MCP write was verified; the documented MCP surface is read-only. Use a separately authorized API or the native UI for mutations and do not attribute those writes to MCP.

04 · Authentication and permissions

For Google Ads, the audited authentication model is: Authentication model is documented by the vendor; inspect the cited source before implementation. The effective permission model is: Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary. Reconfirm the cited first-party source before implementation.

05 · Monitoring, approval, and recovery

Official guide states read-only; API writes must not be attributed to MCP. Official guide states read-only; API writes must not be attributed to MCP.

06 · Gaps and implementation limits

Official guide states read-only; API writes must not be attributed to MCP.

First-party access

Documented surfaces

Google Ads Query Language ↗The Google Ads MCP search tool executes GAQL requests for resource metrics, budgets, and status. The documented MCP server is read-only; accessible customer accounts, OAuth scopes, GAQL grammar, field compatibility, quotas, and reporting limits apply.Source: Google Ads MCP server: Developer integration guide API ↗Developer access Events / extensions ↗Webhooks, apps, or extensions Product ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPOfficial self-hosted MCPCurrent release

Role: provider

Read scope: Strictly read-only: account discovery, GAQL search/reporting, resource metadata

Write scope: No MCP writes verified; the documented surface is read-only.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Official guide states read-only; API writes must not be attributed to MCP.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4

Action access4

Event access4

Identity4

Governance4

Agent access4

UI extensibility3

Portability4

Observability3

Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Google ships these experiences.

Single-platform patterns

Paid-search diagnostic and budget review cockpit
Campaign exception cockpit
Creative and policy review queue
Budget pacing workbench

Use in the brief composer →

Multi-platform compositions

Google Ads + CRM or revenue system: campaign exception cockpit
Google Ads + analytics or warehouse + creative-production platform: cross-system decision workspace

Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources

MCPRepresentative source

https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server ↗

Official guide states read-only; API writes must not be attributed to MCP.

Publisher updated: Jun 29, 2026
BYO-UI reviewed: Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory

https://developers.google.com/google-ads/api ↗

First-party API reference or API overview recorded for this platform.

Publisher updated: Dec 10, 2025
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory

https://developers.google.com/google-ads/api/docs/webhooks ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory

https://ads.google.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.