Amazon Ads
Amazon Ads Report Status MCP
Check an advertising report by its ID to see its current status and any available report information. Available through Nexscope REST and MCP.
Amazon Ads Report Status 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. Resume An Existing Ads Report
Prompt: Use Amazon Ads Reporting to resume report [report ID] for my connected Ads account [connection ID]. Keep the existing report ID and show whether the report is still pending or ready.
What You Need to Provide
The prompt above uses the documented replacement tool; it is not a verified call to this legacy route. The legacy contract is still awaiting clarification.
Use cases for this legacy report route are awaiting clarification: its published request example and MCP argument list disagree. Use the dedicated report-status and report-download tools while this is resolved.
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_data_amazon_ads_developer_proxy_reporting_reports_report_idhttps://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": "data-amazon-ads-developer-proxy-reporting-reports-report-id-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_amazon_ads_developer_proxy_reporting_reports_report_id",
"arguments": {
"body": "{\"reportTypeId\":\"spCampaigns\"}",
"contentType": "application/vnd.createasyncreportrequest.v3+json",
"method": "GET"
}
}
}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 |
|---|---|---|---|
confirmationToken | string | optional | For mutations, first preview without a token, then confirm using the returned single-use token. |
connectionId | integer | required | An Amazon Ads connection owned by the authenticated Nexscope user. |
filters | array | optional | Field and value enumerations are based on the corresponding report-type file. |
filters[] | object | required | Field and value enumerations are based on the corresponding report-type file. |
format | string | optional | Report file format. Default: GZIP_JSON |
includeAmazonSourceUrl | boolean | optional | Whether to return the Amazon presigned source URL. Default: false |
maxAttempts | integer | optional | Maximum number of polls, default waiting window of approximately 10 minutes. Default: 20 |
name | string | optional | Report display name. |
pollInterval | integer | optional | Polling interval in seconds. Default: 30 |
reportId | string | required | Report ID created; creation skipped after passed in. |
serveExtractedFileHttp | boolean | optional | Whether to start the native temporary HTTP service. Default: true |
serveHost | string | optional | Native service binding address. |
servePort | integer | optional | 0 indicates the system allocated port. Default: 0 |
serveSeconds | integer | optional | The number of seconds the local link remains alive. Default: 300 |
skipDepCheck | boolean | optional | Skip dependency checking. Default: false |
timeUnit | string | optional | `DAILY` or `SUMMARY`. Default: SUMMARY |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
success | boolean | optional | Whether downloaded and decompressed successfully. |
reportId | string | optional | Amazon reporting ID. |
status | string | optional | `PENDING`, `PROCESSING`, `COMPLETED` or `FAILED`. |
reportTypeId | string | optional | The type of report requested. |
pollAttempts | integer | optional | Number of times polled. |
elapsedSeconds | number | optional | The number of seconds elapsed. |
downloadPath | string | optional | The downloaded or decompressed local file path. |
extractedFileHttpUrl | string | optional | Native temporary file URL (if enabled). |
serveExpiresAt | string | optional | Native URL expiration time (if returned). |
failureReason | string | optional | Reason for upstream failure when `FAILED`. |
resumeHint.mode | string | optional | `poll-only`。 |
resumeHint.params | object | optional | Reuse the same reportId and increase maxAttempts to continue polling. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
Resume my existing Amazon Ads report without creating another one.
Suggested Steps
Use Amazon Ads Reporting with your owned connection and the existing report ID. Check its returned status and wait for completion before requesting the report content.
About this sample: Legacy-route migration example, not a verified call to this route. Its published request example conflicts with its parameter list. Use /mcp-map/amazon-ads-reporting for the documented resume workflow.
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
Workflow example, not a verified API response.
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
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.