mcp-walmart-ads

Overview Schema Source Related Servers Discussions Admin

call_endpoint

Destructive

Execute authenticated Walmart Connect Ads API requests by operation ID or raw method and path; the server adds signing and auth headers, enabling endpoint calls without manual setup.

Instructions

[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.

Input Schema

TableJSON Schema

Name	Required	Description
`api`	No	Api to call, e.g. walmart:marketplace:order-management. Required with raw method+path; otherwise inferred from operation_id. Src: platforms.
`body`	No	JSON request body for POST/PUT/PATCH — an object, or an array of objects where the API takes a batch.
`path`	No	API path after the base URL, e.g. /v3/orders or /api/v1/campaigns. Required unless operation_id is given.
`method`	No	HTTP method. Required unless operation_id is given.
`params`	No	Query string parameters as a JSON object.
`region`	Yes	Region label, e.g. us. Src: platforms.
`tenant`	No	WAP tenant for non-US walmart:ads regions, e.g. WMT_CA, WMT_MX, WBD_OD. Omit for US and for walmart:marketplace. Sent as wap-tenant-id.
`file_path`	No	Local file to send as multipart/form-data instead of a JSON body — Marketplace feed uploads. Pair with the feedType query parameter.
`environment`	Yes	Target environment. walmart:marketplace accepts production or sandbox; the ads platforms accept whatever the config declares, usually production or staging. Src: platforms.
`path_params`	No	Values for {placeholders} in the path, e.g. {"purchaseOrderId": "1796277083022"}.
`operation_id`	No	Operation id, qualified as api:operationId (e.g. walmart:ads:sponsored-products:SBAProfileUpdateV2) or bare when unambiguous. Resolves the api, platform, method, path, and required headers. Src: operations.
`advertiser_id`	No	Required on walmart:marketplace, where it selects the credential to act as. On the ads platforms it is optional and sent as X-Advertiser-ID, which many display/creative/campaign endpoints require. Src: platforms.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`curl`	No
`error`	No
`cached_at`	No
`truncated`	No
`status_code`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Sep 11, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true/openWorldHint=true, but the description adds real behavioral context beyond them: the server injects auth, signature, market, and correlation headers, and large bodies are truncated to a preview with the full payload available via the returned cached_at resource. That truncation and header-handling disclosure is genuinely useful and not present in the structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, and each subsequent sentence carries distinct information (identification modes, header injection, body truncation). It is dense but earns its length; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with an output schema, the description covers the critical behaviors an agent needs: how to identify the endpoint, that auth is handled server-side, and how oversized bodies are returned. Return values themselves need not be explained given the output schema, though it could say more about the relationship to sibling discovery tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and each parameter is already documented in the schema. The description still adds meaning on top — the operation_id vs method+path+api interaction and the fact that a raw path reaches endpoints absent from the bundled specs — which goes beyond restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource — 'Execute an authenticated API request' — with the concrete identification modes (operation_id, or method + path with an api). This distinguishes it in practice from list_endpoints/describe_endpoint, though it never names a sibling explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the two ways to identify an endpoint and notes that a raw path reaches alpha/beta/unpublished endpoints, which is useful context. However, it never states when to prefer this tool over describe_endpoint or list_endpoints, nor any prerequisite workflow (e.g. resolve operation_id first), leaving usage implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server