Skip to main content
Glama

google_ads_change_history_list

Retrieve recent change history from a Google Ads account to diagnose account activity. Lists change events with timestamps, resource types, operations, and user emails.

Instructions

List the most recent change_event rows on a Google Ads account, sorted newest-first and capped at 100. Returns [{change_date_time (Google-formatted timestamp string returned verbatim from the API — typically 'YYYY-MM-DD HH:MM:SS.ffffff+00:00' but no format coercion is applied, so callers should parse defensively), change_resource_type (enum string e.g. 'CAMPAIGN', 'CAMPAIGN_BUDGET', 'AD_GROUP', 'AD', 'CAMPAIGN_BID_MODIFIER'), resource_change_operation ('CREATE'|'UPDATE'|'REMOVE' as enum string), changed_fields (list of dotted field paths), user_email}]. Read-only. Defaults to the last 14 days when dates are omitted; the API rejects an open-ended range so mureo always fills one. Use this for audit-trail diagnosis. For narrower bid/budget-only filtering use google_ads_cost_increase_investigate.

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.
start_dateNoInclusive start date ('YYYY-MM-DD'). Default: today - 14 days.
end_dateNoInclusive end date ('YYYY-MM-DD'). Default: today.
Behavior4/5

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

Describes return format, read-only nature, default date range, and API quirk of rejecting open-ended range. No annotations provided so description carries burden well, but lacks rate limits or error handling.

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?

Multiple sentences but each adds value. Front-loaded with purpose. Could be slightly more concise.

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?

No output schema, but description explains return fields. Parameter descriptions are in schema. Covers defaults and edge case of open date range. Complete for complexity.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value by explaining return format, defaults, and API behavior beyond what schema provides.

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?

Clearly states it lists change_event rows with sorting and cap. Distinguishes from sibling tool google_ads_cost_increase_investigate for narrower filtering.

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

Usage Guidelines4/5

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

Explicitly says use for audit-trail diagnosis and names a sibling for narrower filtering. Provides default date behavior but could state when not to use more directly.

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