Amazon Ads
Amazon Ads Account Report Creation MCP
Create an advertiser account report for your selected request settings to review Amazon advertising results. Available through Nexscope REST and MCP.
Amazon Ads Account Report Creation 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 A Report Through The Documented Reporting Tool
Prompt: Use Amazon Ads Reporting to request [report type] for my connected account [connection ID] over [start date] to [end date]. Use my validated report configuration and keep the returned report ID for later status checks.
2. Plan Bounded Report Status Checks
Prompt: Use Amazon Ads Reporting to check my existing report [report ID] for account [connection ID]. Prepare a polling plan with [interval in seconds] and [maximum attempts], and verify those limits against the replacement tool before running it. Keep pending, failed and completed reports distinct; stop at the limit.
What You Need to Provide
Use an Amazon Ads connection you own. Never put provider credentials into a prompt or request body.
Changes require a preview followed by separate approval of the exact change. A successful example is not permission to modify an account.
Some legacy fields and operation details are incompletely documented. The examples cover the confirmed workflows; check the stated response and input limitations before using this route.
These are replacement-tool preparation workflows. Legacy polling and file-serving fields describe intent only; validate the current Amazon Ads Reporting contract before executing. No legacy request JSON is supplied.
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_ads_api_v1_create_reportshttps://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-ads-api-v1-create-reports-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_amazon_ads_developer_proxy_ads_api_v1_create_reports",
"arguments": {
"body": "{}",
"contentType": "application/json",
"method": "POST"
}
}
}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 | An Amazon Ads connection owned by the authenticated Nexscope user. |
method | string | required | The three stages of Ads v1 are all `POST`. |
body | string | required | JSON string; account query can be `{}`, report creation/polling see dedicated reference respectively. |
contentType | string | optional | Typically `application/json`. |
pollInterval | integer | optional | 5–300 seconds; official recommendation is to poll every minute. Example: 60 |
maxAttempts | integer | optional | 1–120, default waiting window of approximately 10 minutes. Example: 10 |
reportId | string | optional | After passing in, account mapping and creation will be skipped, and existing reports will only be polled. |
confirmationToken | string | optional | For mutations, first preview without a token, then confirm using the returned single-use token. |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
success | boolean | optional | Whether the entry script completes report processing. |
status | string | optional | `PENDING`, `PROCESSING`, `COMPLETED`, `FAILED` or `STILL_PROCESSING`. |
reportId | string | optional | Report ID. |
reportKind | string | optional | `audience` or `search-impression-share`. |
profileId | number | optional | Ads profile used. |
advertiserAccountId | string | optional | The Ads v1 account ID mapped to. |
fields | array | optional | The actual fixed field combination (as returned). |
totalRows | integer | optional | The total number of rows after merging; 0 is a legally empty report. |
dataFiles[] | array | optional | Local CSV slice file and row number. |
preview[] | array | optional | Results preview. |
resumeHint | object | optional | Continue parameters during STILL_PROCESSING. |
_cacheable | boolean | optional | Successful results are cached for 24 hours; failed/incomplete is false. |
part | integer | optional | Fragment serial number. |
path | string | optional | Local CSV file path. |
rowCount | integer | optional | The number of rows in this shard. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
Use Amazon Ads Reporting to request [report type] for my connected account [connection ID] over [start date] to [end date]. Use my validated report configuration and keep the returned report ID for later status checks.
Suggested Steps
Use Amazon Ads Reporting with your connected account and a validated report configuration. Keep the returned report ID and resume that report if it is still processing; do not create a duplicate merely because it is pending.
About this sample: Workflow illustration only. The legacy contract does not provide enough consistent information to construct a verified request and response pair.
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.