Build the Right Amazon Ads Report
The Amazon Ads Reporting Skill turns a familiar report request or a custom performance question into Reporting API v1 definitions. It includes 17 Sponsored Products, Sponsored Brands, and Sponsored Display template families, with mapping notes for missing fields and split requests. With the Amazon Ads MCP connected, your AI client can resolve the account, validate custom fields against the current catalog or Amazon documentation, submit the report job, retrieve its status, and download the results.
Use it for a clear operating job.
- Known v3 report equivalents
- Ad-hoc fields and grain
- v3-to-v1 reporting migrations
AMC SQL, legacy-v3 execution, current campaign settings, or campaign changes.
Start with the task, then add your scope.
Copy this into a connected client and replace the account, date, ASIN, or threshold details with yours.
Build a Sponsored Products campaign report for the last 30 days with campaign, cost, sales, clicks, impressions, and date grain. Validate every v1 field and the ad-product filter before creating it.A defined result, not a generic answer.
A template-backed or custom v1 report, with the account, grain, field caveats, job status and downloaded results made explicit.
- Report family or business question
- Ad product and advertiser
- Date range and required grain
- Validated field list
- CreateReport JSON
- Unsupported-field caveats
The playbook your agent follows.
- 01
Classify the request
Match a known report family or switch to ad-hoc field discovery.
- 02
Resolve account scope
Separate the active profile from the advertiser account required by reporting.
- 03
Validate fields
Check identifiers, compatibility, periods, and the ad product filter.
- 04
Create and retrieve
Submit the report, retrieve its status, and hand off the download path.
What keeps the workflow dependable.
The context and tools it coordinates.
Give your agent the complete playbook.
Connect Skills once, then start with the prompt above whenever this job comes up.