mcp-walmart-ads
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_endpointsA | [Walmart] List OpenAPI operations across every api. Returned operation ids can be passed straight to describe_endpoint or call_endpoint. |
| describe_endpointA | [Walmart] Describe one OpenAPI operation. Returns it with every components.schemas entry reachable from it, so a request body can be built without the full spec. |
| call_endpointA | [Walmart] Execute an authenticated API request. Identify the endpoint by operation_id, or by method + path with an api — a raw path also reaches alpha/beta/unpublished endpoints absent from the bundled specs. Auth, signature, market, and correlation headers are added by the server. A body over the configured threshold is truncated to a preview; read the returned cached_at resource for the whole of it. |
| download_fileA | [Walmart] Download a report, label, or snapshot. Give a full url — such as the |
| refresh_specsA | [Walmart] Refresh OpenAPI specs into the user cache, which then takes precedence over the bundled copies. Omit api to refresh all 33. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| platforms | [Walmart] List every platform, its auth model, and the regions and environments it declares. A platform with no regions cannot be called — read one of its sub-resources to be told why. oauth2 platforms require an advertiser_id; signature platforms do not. Src: platforms. |
TDQS
Scored across 5 tools
Each tool has a distinct role: list (enumerate operations), describe (inspect a schema), call (execute JSON requests), download (fetch binary files), refresh (update specs). The only mild overlap is that call_endpoint and download_file both accept operation_id or api+method+path, but their output semantics (JSON response vs. binary file) are clearly separated in the descriptions.
All five tools follow a clean verb_noun snake_case pattern (list_endpoints, describe_endpoint, call_endpoint, download_file, refresh_specs). The singular/plural difference between describe_endpoint and list_endpoints is a trivial, intuitive deviation.
Five tools is a well-scoped set for a meta-API wrapper: discovery, inspection, execution, file retrieval, and cache refresh. Nothing feels redundant or missing at the count level.
The set covers the full lifecycle of an OpenAPI-driven client: enumerate operations, describe schemas to build bodies, execute authenticated calls, download binary artifacts, and refresh specs including alpha/beta endpoints absent from bundled specs. There are no obvious dead ends for the stated purpose.