Amazon Ads API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_METHOD | No | Authentication method - 'direct' for BYOA or 'openbridge' for partner app | |
| AMAZON_AD_API_PACKAGES | No | Comma-separated list of tool packages to activate (e.g., 'profiles,amc-workflow') | |
| AMAZON_AD_API_CLIENT_ID | No | Your Amazon Ads API client ID (required for BYOA) | |
| OPENBRIDGE_REFRESH_TOKEN | No | Your Openbridge API token (required when using Openbridge partner app) | |
| AMAZON_AD_API_CLIENT_SECRET | No | Your Amazon Ads API client secret (required for BYOA) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tagsA | List available tool tags. Use to browse available tools by tag before searching. |
| searchB | Search for available tools by query. Returns matching tools ranked by relevance. |
| get_schemaA | Get parameter schemas for specific tools. Use after searching to get the detail needed to call a tool. |
| executeA | Run async Python in a sandboxed interpreter. The whole script runs as one
turn; use Available in scope:
Sandbox guardrails (Monty interpreter):
Auth, region, and active profile are managed by the server. Do not pass
Session-scope contract:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| auth_profile_setup | Complete authentication and profile setup for Amazon Ads API |
| export_entity_download | Request entity export, poll status, and download when ready |
| create_campaign | Create a new advertising campaign with proper validation |
| troubleshoot_api_error | Diagnose and recover from common API errors |
| generate_async_report | Create and retrieve an async report with polling |
| setup_region | Configure region for API routing |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: 'tags' lists tags, 'search' searches tools, 'get_schema' retrieves schemas, and 'execute' runs sandboxed Python. No overlap or ambiguity.
Tool names are mixed: 'tags' is a noun, 'search' and 'execute' are verbs, 'get_schema' is verb_noun. They are readable but lack a consistent pattern.
With 4 tools, the set is compact and appropriate for a meta-server focused on discovery and execution. Not too many or too few.
The server claims to be for the Amazon Ads API but provides only meta-tools. Core API operations (e.g., listing campaigns, creating ads) are missing, leaving a significant gap for the stated purpose.