amazon-ads-mcp

get_change_history

Read-only

Retrieve detailed change history for Amazon Ads entities, showing what changed, from what, to what, and when, for up to 90 days. Filter by entity type, change type, or campaign.

Instructions

What changed, from what, to what and when (up to 90 days back).

since: ISO date or datetime; otherwise the last days days. entity_types: CAMPAIGN, AD_GROUP, AD, KEYWORD, NEGATIVE_KEYWORD, PRODUCT_TARGETING. changes: BID_AMOUNT, STATUS, BUDGET_AMOUNT, CREATED, PLACEMENT_GROUP, ...

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>"
    },
    "name": "get_change_history"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`since`	No
`market`	Yes
`changes`	No
`entity_ids`	No
`campaign_ids`	No
`entity_types`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety. It adds the 90-day time window constraint, which is useful behavioral context. It doesn't describe output format (output schema exists) or any side effects, so it adds some value beyond annotations but not extensive.

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?

The description is concise, front-loading the purpose in the first line. The parameter notes are terse and efficient. However, the use of an ellipsis '...' in the changes list is incomplete and slightly sloppy, and the structure could be improved with clear sections for each parameter.

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

Completeness2/5

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

With 7 parameters, 0% schema coverage, and an output schema present, the description is insufficient for an agent to call the tool correctly. It explains some parameters but omits key ones like market, entity_ids, and campaign_ids, and doesn't clarify the meaning of the allowed values. The agent would have to guess or rely on external knowledge.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. It explains 'since' and its relationship to 'days', and lists allowed values for entity_types and changes (with an ellipsis). However, it leaves market, entity_ids, and campaign_ids completely unexplained, which is a significant gap for a 7-parameter tool with a required market parameter.

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 clearly states the tool returns change history with details of what changed, from what, to what, and when. It distinguishes itself from siblings like get_suggested_bids or run_report by its explicit focus on change history. However, it doesn't explicitly contrast with any specific sibling, so it's clear but not differentiated.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. It doesn't mention any context like 'use for auditing changes' or exclude cases where other tools are better. The description is purely declarative and offers no usage direction.

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

Deploy Server