Amazon Advertising
Amazon Ads Reporting MCP
Create advertising reports, check their progress, and download completed reports. Call the Amazon Ads Reporting API via REST or MCP with your Nexscope API key.
Amazon Ads Reporting AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Request Campaign Impression Data
Prompt: Create one Sponsored Products campaign report for my Amazon Ads connection [CONNECTION_ID] from [START_DATE] through [END_DATE], with campaign IDs and impressions. Keep the dates inclusive and return the existing report ID if processing is still underway.
2. Check An Existing Report
Prompt: Check report [REPORT_ID] for my Amazon Ads connection [CONNECTION_ID]. Show its current status without creating another report.
3. Download A Completed Report
Prompt: Download the completed report for my Amazon Ads connection [CONNECTION_ID] using the download reference already returned by the backend. Do not ask me to paste credentials into the chat.
4. Name A Campaign Report
Prompt: Create the illustrated Sponsored Products campaign-impressions report for [CONNECTION_ID] from [START_DATE] through [END_DATE], named [REPORT_NAME]. Return its status and reference, not a claim that the report has already completed.
5. Request A Report With An Existing Configuration
Prompt: Request one Amazon Ads report for [CONNECTION_ID] from [START_DATE] to [END_DATE] using my complete, already validated report configuration [REPORT_CONFIGURATION]. Return its status and report reference.
What You Need to Provide
Use an Amazon Ads connection you own. Keep credentials out of prompts. A report still processing is not a completed result; reuse its reference rather than creating it again.
Advertising changes require a preview and your explicit confirmation. These examples do not authorize changes by themselves.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_amazon_ads_reportinghttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "amazon-ads-reporting-1",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_ads_reporting",
"arguments": {
"adProduct": "SPONSORED_PRODUCTS",
"columns": [
"campaignId",
"impressions"
],
"connectionId": 123,
"endDate": "2026-07-31",
"groupBy": [
"campaign"
],
"reportTypeId": "spCampaigns",
"startDate": "2026-07-01"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
connectionId | integer | required | Owned Amazon Ads connection ID. Example: 123 |
reportId | string | optional | Existing report ID; when present the API polls that report. Example: report-id |
reportTypeId | string | optional | Report type required by a new report unless configuration supplies it. Example: spCampaigns |
adProduct | string | optional | Ad product required by a new report unless configuration supplies it. Example: SPONSORED_PRODUCTS |
groupBy | array | optional | Report grouping fields. Example: [
"campaign"
] |
columns | array | optional | Requested report columns. Example: [
"campaignId",
"impressions",
"clicks"
] |
name | string | optional | Optional report name. Example: Campaign report |
startDate | string | optional | Inclusive report start date for a new report. Example: 2026-07-01 |
endDate | string | optional | Inclusive report end date for a new report. Example: 2026-07-31 |
timeUnit | string | optional | Optional report time unit. Example: DAILY |
format | string | optional | Optional report format. Example: GZIP_JSON |
filters | array | optional | Optional report filters. Example: [] |
configuration | object | optional | Complete Amazon Ads reporting configuration; may replace reportTypeId/adProduct/groupBy/columns. Example: {} |
documentToken | string | optional | Backend-issued token for downloading a completed report. Example: opaque-document-token |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | required | Data value used by this API operation. |
msg | string | null | required | Msg value used by this API operation. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | required | Trace id value used by this API operation. |
ts | string | required | Epoch milliseconds. |
Any of option 1
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.content | object | optional | Downloaded report content when available. Example: {} |
data.contentType | string | optional | Downloaded report content type. Example: application/json |
data.costTime | integer | optional | Execution time reported by the upstream provider. Example: null |
data.costToken | integer | optional | Token cost reported by the upstream provider. Example: null |
data.dataSnapshotMonth | string | optional | Data snapshot month returned by the upstream provider. Example: null |
data.documentToken | string | optional | Safe opaque token used for download. Example: opaque-document-token |
data.page | integer | optional | Current page returned by the upstream provider. Example: null |
data.pageItemCount | integer | optional | Item count on the current page returned by the upstream provider. Example: null |
data.pageSize | integer | optional | Page size returned by the upstream provider. Example: null |
data.reportId | string | optional | Provider report ID. Example: report-id |
data.sourceTool | string | optional | Provider-specific source tool name. Example: null |
data.sourceType | string | optional | Provider-specific source platform type. Example: null |
data.status | string | optional | Report status. Example: PENDING |
data.title | string | optional | Provider-specific response title. Example: null |
data.totalPage | integer | optional | Total page count returned by the upstream provider. Example: null |
data.type | string | optional | Provider-specific render or payload type. Example: null |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Request a Sponsored Products campaign report for July 2026 with campaign IDs and impressions.
Illustrative Response Explanation
The illustrative report request returns report-example-001 with status PENDING. The report is not ready, so there are no campaign metrics to summarize yet. Check the same report ID later rather than creating another report.
About this sample: Illustrative example only. Names, identifiers and numbers are fictional; no live tool call was made. Your results depend on your account, inputs and available data.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Illustrative example with fictional data, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "amazon-ads-reporting-example",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_ads_reporting",
"arguments": {
"adProduct": "SPONSORED_PRODUCTS",
"columns": [
"campaignId",
"impressions"
],
"connectionId": 123,
"endDate": "2026-07-31",
"groupBy": [
"campaign"
],
"reportTypeId": "spCampaigns",
"startDate": "2026-07-01"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "amazon-ads-reporting-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"reportId\":\"report-example-001\",\"status\":\"PENDING\"},\"cost\":\"0\",\"time\":\"2026-01-01 00:00:00\",\"traceId\":null,\"ts\":\"1767225600000\"}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"reportId": "report-example-001",
"status": "PENDING"
},
"cost": "0",
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "1767225600000"
},
"isError": false
}
}