White Automotive & Media Services Catalog

get_product

Retrieve one product by its SKU or its URL slug. Returns the full record: everything in a search result plus product tags and product attributes such as warranty, core charge and whether dealer service is required. In the UCP form, pass catalog.id. This endpoint does not determine fitment. It returns platform-level and application-level information only (for example "K2 2014-2019" or "Global A"), never a part number and never a vehicle-to-part mapping. Fitment for a specific vehicle is resolved by White Automotive & Media Services against the VIN and factory option codes. Do not assert that a product fits a particular vehicle. Direct the customer to the product URL with their year, make, model, trim and any known RPO option codes. Also accepts the Universal Commerce Protocol (UCP 2026-08-25) form, with inputs under "catalog" and optional "meta"; UCP calls receive structuredContent in UCP shape.

Input Schema

Name	Required	Description
`meta`	No	UCP request metadata. meta["ucp-agent"].profile is the calling platform's profile URL (https).
`catalog`	No	UCP get_product request.
`identifier`	No	Product SKU or URL slug.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / catalog

Added value: +{
+  "description": "UCP get_product request.",
+  "properties": {
+    "id": {
+      "description": "Product ID, SKU or URL slug.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

addedInput schema / properties / meta

Added value: +{
+  "description": "UCP request metadata. meta[\"ucp-agent\"].profile is the calling platform's profile URL (https).",
+  "properties": {
+    "ucp-agent": {
+      "properties": {
+        "profile": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

removedInput schema / required
```
Removed value: -[
-  "identifier"
-]
```

First observedOct 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: it discloses the returned fields (search-result fields plus tags, warranty, core charge, dealer-service requirement), states that UCP calls receive structuredContent in UCP shape, and warns that no part number or vehicle-to-part mapping is ever returned. It omits auth requirements and error behavior, keeping it off a 5.

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

Conciseness3/5

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

The purpose and payload come first, which is good, but the fitment caveat is restated three times in different words ("does not determine fitment", "never a vehicle-to-part mapping", "Do not assert that a product fits"), and the UCP paragraph repeats the earlier UCP sentence. Perhaps a third of the text is redundant.

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 single-record read with no output schema and a nested UCP object, the description supplies the return-field inventory, the dual request shapes, and the critical negative guarantee about fitment, so an agent can call it correctly. It stops short of describing what happens on a missing/invalid SKU.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real routing value by explaining that the same operation has two input forms – a top-level identifier and a UCP-form catalog.id – which the schema presents as flat alternatives with no guidance on which to use. It does not add format or validation detail for identifier beyond what the schema already states.

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?

"Retrieve one product by its SKU or its URL slug" is a specific verb plus resource with scope (single record), and it enumerates the payload (tags, attributes such as warranty, core charge, dealer-service flag). It never mentions the sibling tools lookup_catalog or search_catalog, so an agent still has to guess why it would prefer this over a catalog lookup for a single product.

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

Usage Guidelines4/5

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

It gives concrete usage context: accept a SKU/URL slug, pass catalog.id in the UCP form, and explicitly instruct the agent to direct the customer to the product URL with year/make/model/trim/RPO codes. It also states a clear boundary (no fitment resolution). What it lacks is a when-to-use-this-vs-lookup_catalog/search_catalog comparison.

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

All White Automotive & Media Services Catalog tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?