Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get report

amazon_ads_get_report
Read-onlyIdempotent

Check an Amazon Ads report job once and, when complete, read its native rows via the jobToken from report creation. Supports bounded pagination with row offsets and partial-result flags.

Instructions

Check an Amazon report once and, when complete, read its native rows. Use only the jobToken returned by amazon_ads_create_report for this profile. Downloads are bounded; pagination returns row offsets and marks partial results. Expired reports must be requested again.

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": {
      "accountId": "<accountId>",
      "jobToken": "<jobToken>"
    },
    "name": "amazon_ads_get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows returned by this call, up to 1000.
offsetNoZero-based index of the first row to return. Use nextOffset from the previous call.
jobTokenYesOpaque job token returned by amazon_ads_create_report for this profile. Valid for seven days.
accountIdYesAdvertising profile ID listed in AMAZON_ADS_PROFILE_IDS, such as 1234567890. The region-qualified form used by hosted getmcpads, such as EU:1234567890, is accepted when its region matches AMAZON_ADS_REGION.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed1 schema field changedv1.0.1
    • 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"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description adds real value by disclosing bounded download size, offset-based pagination with partial-result markers, and seven-day expiry semantics. It stops short of describing what a single check returns when the report is still incomplete, which is the main behavioral question for a poll tool.

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?

Four short sentences, each earning its place: check semantics first, token constraint second, pagination/bound behavior third, expiry fallback last. No filler or repetition of schema detail.

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

Completeness5/5

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

With an output schema present and annotations covering safety, the remaining gaps an agent needs are expiry, bounded download, and offset pagination — all covered. Nothing required to invoke the tool correctly is missing.

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% and every parameter (limit, offset, jobToken, accountId) is documented in the schema, including nextOffset guidance and region-qualified accountId form. The description's jobToken note largely restates the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Check an Amazon report ... read its native rows') and positions itself relative to the sibling amazon_ads_create_report, which produces the jobToken. An agent can tell it is a fetch/poll tool rather than a report-creation tool without opening either schema.

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?

Explicit that only jobTokens from amazon_ads_create_report for the same profile are valid, and that expired reports must be re-requested, which is a clear exclusion path. It does not spell out the polling cadence or that a not-yet-complete report should be re-checked rather than recreated, so context is clear but not exhaustive.

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