Santa Wishlist – hand-picked gift ideas

Search kids gifts

search_gifts

Read-only

Search kids Christmas gift ideas for the user's store (amazon.com for US, amazon.se default). Returns kids-filtered search link cards + curated catalogMatches (English on amazon.com). q is optional. OpenAPI: searchAmazon.

Input Schema

Name	Required	Description
`q`	No	Search query, e.g. LEGO City (default: christmas gifts for kids)
`limit`	No
`locale`	No	User locale, e.g. en-US, sv, de. en-US switches to amazon.com when marketplace is omitted.
`ageBand`	No
`country`	No	ISO country of the shopper, e.g. US or SE (used when marketplace is omitted)
`interest`	No	Category filter
`marketplace`	No	Amazon storefront for the end user: amazon.com (US) or amazon.se (Sweden, default); also uk, de, fr… Order: marketplace → country → locale/Accept-Language (en-US ⇒ amazon.com) → amazon.se. amazon.se returns curated /dp product links; amazon.com returns English search links tagged for amazon.com.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "ISO country of the shopper, e.g. US or SE (used when marketplace is omitted)",
+  "type": "string"
+}

changedInput schema / properties / locale / description

Previous value: -"User locale, e.g. en, sv, de, fr, es"New value: +"User locale, e.g. en-US, sv, de. en-US switches to amazon.com when marketplace is omitted."

removedInput schema / properties / locale / minLength
```
Removed value: -2
```

changedInput schema / properties / marketplace / description

Previous value: -"Amazon storefront domain or id for the end user, e.g. amazon.se, amazon.com, se, de. REQUIRED — curated ASINs only produce /dp links on amazon.se; other marketplaces get search deep-links."New value: +"Amazon storefront for the end user: amazon.com (US) or amazon.se (Sweden, default); also uk, de, fr… Order: marketplace → country → locale/Accept-Language (en-US ⇒ amazon.com) → amazon.se. amazon.se returns curated /dp product links; amazon.com returns English search links tagged for amazon.com."

removedInput schema / properties / marketplace / minLength
```
Removed value: -2
```

changedInput schema / properties / q / description

Previous value: -"Search query, e.g. LEGO City"New value: +"Search query, e.g. LEGO City (default: christmas gifts for kids)"

removedInput schema / properties / q / minLength
```
Removed value: -1
```

removedInput schema / required

Removed value: -[
-  "q",
-  "marketplace",
-  "locale"
-]

First observedOct 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already mark this as a read-only, open-world tool, and the description adds meaningful behavioral detail: marketplace-dependent output, English results on amazon.com, and curated /dp product links on amazon.se. It stops short of describing error behavior or limits, but the marketplace-specific return behavior is useful context.

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?

The description is compact and front-loads the main purpose and return behavior. The final 'OpenAPI: searchAmazon' line is an implementation reference that does little for an agent, but the rest is dense and readable.

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?

Given seven optional parameters, no required fields, and no output schema, the description does a reasonable job explaining default query behavior, marketplace selection, and return formats. It is not fully complete on parameter semantics or sibling routing, but it covers what is needed for a basic call.

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 71%, so most parameters already have semantic documentation. The description only reinforces that q is optional and that amazon.com is used for US while amazon.se is the default; it adds little for limit, ageBand, locale, country, or interest.

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 and resource: search kids Christmas gift ideas for the user's store. It also clarifies the return shape (search link cards plus curated catalogMatches), but it does not explicitly distinguish this tool from siblings such as get_catalog or resolve_product.

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 description implies the use case by naming kids Christmas gift search, and notes that q is optional with defaults. However, it does not state when to use this tool versus siblings or when not to use it.

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

All Santa Wishlist – hand-picked gift ideas 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?