Kroger MCP Server

Overview Schema Source Related Servers Discussions Admin

bulk_search_products

Search multiple grocery products in one call to reduce round-trips, with optional brand, fulfillment, result-limit, and store-location filters.

Instructions

Search for multiple products in a single tool call to reduce round-trips.

Input Schema

Name	Required	Description	Default
`searches`	Yes	List of search queries (1-25). Each item should have: - term: The search term (e.g., "milk", "bread"); 3+ characters, at most 8 words - limit: Number of results per search (1-50, default: 10) - fulfillment: Optional fulfillment filter ("ais", "csp", "dth", "sth") - brand: Optional brand filter (case-sensitive)
`location_id`	No	8-character store locationId, for example 01400513. Defaults to the preferred location set with set_preferred_location.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 27, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about per-search error handling, whether results are grouped in input order, auth/location requirements, or behavior when one search in the batch fails. 'Reduce round-trips' is the only behavioral hint.

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?

A single front-loaded sentence with no filler. It is short but borders on under-specification rather than redundancy.

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

Completeness2/5

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

For a batched operation with 25-item fan-out, the description should at minimum explain how results map back to individual searches and how partial failures surface; neither is covered. The output schema covers return values, but the batching semantics that an agent most needs are absent.

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 100%, including per-field descriptions for term, brand, limit, fulfillment, and location_id, so the baseline is 3. The description adds no parameter meaning beyond 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?

States a specific verb+resource (search multiple products in one call) and the distinguishing trait versus the singular sibling: batching. It doesn't name search_products directly, so the differentiation is implied rather than explicit.

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 clause 'to reduce round-trips' implies when to reach for this instead of search_products, but there is no explicit when/when-not guidance, no mention of the 1-25 search cap as a routing constraint, and no alternative named.

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