mcp-walmart-marketplace

Overview Schema Source Related Servers Discussions Admin

download_file

Read-only

Download Walmart Marketplace reports, labels, or binary payloads to a local file using a direct URL or API operation reference, with automatic redirect handling and secure credential removal.

Instructions

[WalmartMarketplace] Download a report, label, or other binary payload to a local path. Give a full url, or operation_id (or method and path). Follows redirects and drops credentials when a redirect leaves Walmart's host.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	[WalmartMarketplace] Absolute URL to fetch, e.g. a report URL returned by a previous call.
`path`	No	[WalmartMarketplace] API path when not using url.
`method`	No	[WalmartMarketplace] HTTP method when using path.
`params`	No	[WalmartMarketplace] Query string parameters.
`region`	Yes	[WalmartMarketplace] Region label, e.g. us. Src: config.
`dest_path`	Yes	[WalmartMarketplace] Local path to write the downloaded bytes to.
`environment`	Yes	[WalmartMarketplace] Target environment — production or sandbox. Src: config.
`path_params`	No	[WalmartMarketplace] Values for {placeholders} in path.
`operation_id`	No	[WalmartMarketplace] Operation id as domain:operationId. Src: operations.
`advertiser_id`	Yes	[WalmartMarketplace] Advertiser (seller profile) id to act as. Src: config.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`urls`	No
`error`	No
`status_code`	No
`content_type`	No
`bytes_written`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the read-only nature is covered. The description adds valuable behavioral context: it follows redirects and drops credentials when redirecting away from Walmart's host. This goes beyond the annotations and informs the agent of security-relevant behavior.

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

Conciseness5/5

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

The description is two sentences with zero waste. The primary purpose is stated first, followed by essential behavioral detail about redirects. Every sentence earns its place and the structure is front-loaded.

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 download tool with 10 parameters and read-only annotations, the description covers the key usage scenarios and security behavior. It does not mention output schema or file handling details, but the presence of an output schema and the tool's straightforward nature make this acceptable. Overall, it is complete enough for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters have individual descriptions. The tool description adds value by clarifying the relationship between url, operation_id, and method/path (i.e., you can use one of these alternatives), which is not evident from the schema alone. However, it does not add syntax or format details beyond that.

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

Purpose5/5

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

The description clearly states the action (download), the resource type (report, label, or other binary payload), and the destination (local path). It also lists multiple ways to specify the target (full url, operation_id, or method+path), making the tool's purpose distinct from siblings like call_endpoint which are for API calls.

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?

The description explains how to invoke the tool (via url, operation_id, or method+path) but does not explicitly contrast it with sibling tools or state conditions for when to choose this over call_endpoint or upload_feed. The context of binary payload download is implied but not made explicit against alternatives.

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

Deploy Server