Amazon Ads
Sponsored Products Budget Rules MCP
Work with budget rules to control when advertising campaign budgets are adjusted for Sponsored Products. Available through Nexscope REST and MCP.
Sponsored Products Budget Rules 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. Review Sponsored Products Budget Rules
Prompt: List sponsored products budget rules for my connected Amazon Ads account [connection ID]. Show only the returned records and state whether more results remain; do not change any settings. Read one page of up to 20 records and stop; leave automatic page collection off.
2. Create Sponsored Products Budget Rules
Prompt: Prepare a preview to create sponsored products budget rules for my connected Amazon Ads account [connection ID], using [my proposed settings and target identifiers]. Show the affected entities and wait for my approval before applying the exact change.
3. Update Sponsored Products Budget Rules
Prompt: Prepare a preview to update sponsored products budget rules for my connected Amazon Ads account [connection ID], using [my proposed settings and target identifiers]. Show the affected entities and wait for my approval before applying the exact change.
4. Review A Limited Set Of Sponsored Products Budget Rules
Prompt: Review up to 20 sponsored products budget rules records for my connected Amazon Ads account [connection ID]. Read one page only, leave automatic page collection off, and tell me whether additional results remain.
5. Apply The Exact Approved Change
Prompt: After I explicitly approve the preview for sponsored products budget rules in account [connection ID], apply that exact change once. If the preview has expired or my requested settings change, prepare a new preview instead of reusing the earlier approval.
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.
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_sp_budget_ruleshttps://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-sp-budget-rules-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_amazon_ads_developer_proxy_sp_budget_rules",
"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. |
fetchAll | boolean | optional | Automatic page turning; SP and SB V4 main resource lists use `nextToken`, SB Target/BudgetRule uses `nextToken` (BudgetRule query must contain `pageSize`), SB Keyword GET, SB V3 GET and SD use `startIndex + count`. Example: true |
maxResults | integer | optional | Single page 1–100; SD corresponds to count. Example: 100 |
skipDepCheck | boolean | optional | Skip dependency checking. Example: false |
includeExtendedDataFields | boolean | optional | Some entities return extended fields; SD is switched through the /extended path. |
locale | string | optional | Localization parameters (supported by some keyword scripts). |
method | string | required | Upstream HTTP methods: list query `GET`, create `POST`, modify `PUT`. |
body | string | optional | Provide payload when creating/modifying; not required for list query. You cannot put an Amazon access token into the payload. |
contentType | string | optional | application/json。 |
queryString | string | optional | Pass upstream query parameters when needed. |
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 API completed the call successfully. |
apiVersion | string | optional | `V3` or `V4` (if provided by the script). |
amazonResourceVersion | string | optional | The actual Amazon resource version (if provided by the script). |
budgetRules | array | optional | Budget rules array; actual fields returned by Amazon. |
total | integer | optional | The number of aggregated entries (if provided by the script). |
pagesFetched | integer | optional | Number of pages obtained. |
truncated | boolean | optional | Whether it was truncated due to paging limit. |
name | string | optional | Name (returned if supported by the entity). |
state | string | optional | `ENABLED`, `PAUSED` or `ARCHIVED` (SD upstream may use lowercase). |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Show one page of sponsored products budget rules for my connected Ads account.
Illustrative Response Explanation
The illustrative response returns no sponsored products budget rules records on this page. It does not prove that the account has no matching records outside the requested scope, and no settings were changed.
About this sample: Illustrative fictional data, not a live tool call. This is one bounded page. A zero returned count must not be presented as a market-wide or unfiltered-account total.
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": "data-amazon-ads-developer-proxy-sp-budget-rules-example",
"method": "tools/call",
"params": {
"name": "nexscope_data_amazon_ads_developer_proxy_sp_budget_rules",
"arguments": {
"connectionId": 123,
"method": "GET",
"fetchAll": false,
"maxResults": 20
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "data-amazon-ads-developer-proxy-sp-budget-rules-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"success\":true,\"budgetRules\":[],\"total\":0,\"pagesFetched\":1,\"truncated\":false}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"success": true,
"budgetRules": [],
"total": 0,
"pagesFetched": 1,
"truncated": false
}
},
"isError": false
}
}