Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

walmart_category

Read-onlyIdempotent

Browse and retrieve parsed products from any Walmart category using its category ID. Get structured product lists with pagination for catalog building or category monitoring.

Instructions

Browse parsed products within a Walmart category by category ID.

    Returns a structured list of products in a Walmart category, with
    pagination.

    When to use:
    - Exploring products within a specific Walmart department/category
    - Building category-level catalogs or monitoring a category

    When NOT to use:
    - Free-text product discovery (use 'walmart_search')

    Args:
        params (WalmartCategoryParams): category (required) plus optional
            page, tld, country_code, and output_format.

    Returns:
        str: JSON (default) or CSV containing the category product list.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Adds context about pagination, error conditions (ToolError), and output format options beyond the annotations which already indicate idempotent and non-destructive behavior. Does not contradict annotations.

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?

Well-structured with headings, concise yet informative. Every sentence adds value.

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?

Output schema exists; description mentions return formats and errors. With rich annotations and sibling distinctions, coverage is good. Missing details on pagination behavior (e.g., max pages) but overall complete.

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 coverage is 0%, so description must compensate. It lists the parameters but only briefly repeats the schema's own descriptions without adding significant detail. Adequate but not exceptional.

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?

Description clearly states it browses parsed products within a Walmart category by ID, with pagination. Distinguishes from 'walmart_search' for free-text discovery.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections, clearly pointing to walmart_search as alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scraperapi/scraperapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server