Amazon Advertising
Amazon Ads SP Insights Report Status MCP
Check whether your Amazon Ads insights report is still processing or ready to download. Use the existing report ID to track its status.
Amazon Ads SP Insights 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. Check Report Progress
Prompt: Check the current status of report [REPORT_ID] for my Amazon Ads connection [CONNECTION_ID]. Do not create a new report. If it is still processing, return the status so I can check again later.
2. Identify Completed Report Parts
Prompt: Check the current status of report [REPORT_ID] for my Amazon Ads connection [CONNECTION_ID]. Do not create a new report. If it is still processing, return the status so I can check again later. List the completed parts available for download and distinguish them from a report still processing. Keep backend download references private; stop after this status check.
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_sp_insights_report_statushttps://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-sp-insights-report-status-1",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_ads_sp_insights_report_status",
"arguments": {
"connectionId": 123,
"reportId": "report-id"
}
}
}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; profile and region are resolved by the backend. Example: 123 |
reportId | string | required | Existing report ID; polling never creates another report. Example: report-id |
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 — requires reportId
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.completedReportParts | array | optional | Completed CSV parts; each part contains a backend documentToken instead of a signed URL. Example: [] |
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.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 | required | Created or queried report identifier. Example: report-id |
data.reportParts | array | optional | Provider alias for completed parts, when present. Example: [] |
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 | Provider report state when present. 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
Is report-example-001 ready to download?
Illustrative Response Explanation
The illustrative status is PENDING. No completed report or download token has been returned yet; check this same report again later.
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-sp-insights-report-status-example",
"method": "tools/call",
"params": {
"name": "nexscope_amazon_ads_sp_insights_report_status",
"arguments": {
"connectionId": 123,
"reportId": "report-example-001"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "amazon-ads-sp-insights-report-status-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
}
}