Amazon Ads
Amazon Ads: store Tokens API
Amazon Ads: store Tokens API.
MCP tool name
nexscope_data_amazon_ads_store_tokensMCP endpoint
https://api.nexscope.ai/mcpJSON-RPC method
tools/callAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxIf authentication fails, ask the user to open API Access and copy a valid key.
Call this MCP tool
Initialize 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-store-tokens-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_amazon_ads_store_tokens",
"arguments": {}
}
}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. Example: {} |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
authRecordId | number | optional | Authorization record ID. Example: {} |
tokenType | string | optional | Token type, typically `bearer`. Example: {} |
expiresIn | string / number | optional | Access token validity period, usually about 3600 seconds. Example: {} |
Examples
Example arguments
{}Example structuredContent
{
"code": 0,
"cost": "-1",
"data": {},
"msg": null,
"time": "2026-01-01 00:00:00",
"traceId": null,
"ts": "0"
}