Skip to main content
Glama
alyiox

mcp-walmart-ads

by alyiox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-walmart-ads

No user-submitted related servers found.

    Related Servers

    • mcp-walmart-marketplace

      alyiox
      A
      license
      A
      quality
      B
      maintenance
      This MCP server enables interaction with Walmart Marketplace APIs, offering tools for managing items, orders, inventory, prices, promotions, feeds, and more, with automatic OAuth2 authentication and spec-driven endpoint discovery.
      6
      MIT

    • vibe-agent-mcp

      yagaMI-Reverse
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Vibe-Marketer Agent API that enables generating ads, auditing landing pages, and running local preflight checks on ad compliance, with an autonomous agent loop to improve results.
      -

    • walmart-mcp

      luke-nielsen
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server for Walmart Marketplace and Affiliate APIs, enabling sellers to manage items, inventory, prices, and orders, and consumers to search, lookup products, reviews, and store locations.
      7 npm
      MIT

    • walmart-marketplace-mcp

      hey-nate
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets you manage a Walmart Marketplace seller account in plain language, including orders, inventory, pricing, returns, WFS fulfillment, and reports.
      MIT

    • amazon-mcp

      coaxon
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Amazon Selling Partner API and Advertising API, enabling access to orders, inventory, pricing, ads, and reports via natural language.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources