Kroger MCP Server

Overview Schema Source Related Servers Discussions Admin

search_products_by_id

Retrieve product details by entering a 13-digit UPC or product ID, optionally specifying a store location for localized results.

Instructions

Search for products by their specific product ID.

Input Schema

Name	Required	Description	Default
`product_id`	Yes	13-digit productId or UPC, for example 0001111041700. Get one from search_products.
`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.

Changed8 schema fields changedv0.4.0Oct 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / location_id / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^[A-Za-z0-9]{8}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / location_id / description

Added value: +"8-character store locationId, for example 01400513. Defaults to the preferred location set with set_preferred_location."

removedInput schema / properties / location_id / title
```
Removed value: -"Location Id"
```

addedInput schema / properties / product_id / description

Added value: +"13-digit productId or UPC, for example 0001111041700. Get one from search_products."

addedInput schema / properties / product_id / pattern
```
Added value: +"^[0-9]{13}$"
```
removedInput schema / properties / product_id / title
```
Removed value: -"Product Id"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only lookup via 'Search,' but says nothing about whether the location defaults to a preferred store (that detail lives only in the schema), whether a miss returns empty vs. an error, or any rate or availability constraints.

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 efficient but so thin that the brevity comes at the cost of routing information rather than being a model of density.

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

Completeness3/5

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

An output schema exists and the parameter schema is fully documented, so return values and argument formats are covered elsewhere. What remains missing is sibling differentiation and any hint of usage context, which matters given how many product-related siblings exist.

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%, and the schema already explains the 13-digit UPC format and the 8-character location ID with its default from set_preferred_location. The description adds nothing beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource: search for products by product ID. The distinction from siblings is missing, though — it does not clarify how this differs from search_products, bulk_search_products, or get_product_details, which all sound like they could return product data.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives despite several overlapping siblings. An agent can infer this is the single-ID lookup path, but nothing in the text says so or says when not to reach for it.

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