Santa Wishlist – hand-picked gift ideas

One-shot create and fill

create_and_fill

One call: create a curated kids' Christmas gift wishlist and return shopUrl (share link) + ownerUrl. Preferred agent path: create a wishlist and add ASINs / keywords / search queries in one call (or give only ageBand/interests to auto-fill curated picks). Pass marketplace=amazon.com for US shoppers (amazon.se default). Returns id, editToken, shopUrl, ownerUrl, parentUrl, kidUrl. OpenAPI: agentCreateAndFill.

Input Schema

Name	Required	Description
`count`	No	If no items are given, auto-fill this many curated picks for the age band/interests (default 6)
`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)
`childName`	No
`interests`	No
`itemAsins`	No
`itemQueries`	No	Each query is searched and added as a wish
`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.
`itemKeywords`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026

addedInput schema / properties / count

Added value: +{
+  "description": "If no items are given, auto-fill this many curated picks for the age band/interests (default 6)",
+  "maximum": 12,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / country

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

addedInput schema / properties / locale

Added value: +{
+  "description": "User locale, e.g. en-US, sv, de. en-US switches to amazon.com when marketplace is omitted.",
+  "type": "string"
+}

addedInput schema / properties / marketplace

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

First observedOct 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes further by spelling out return fields, the marketplace resolution order (marketplace → country → locale → amazon.se default), and the different link types per storefront. It omits any auth/permission or rate-limit expectations for a write operation.

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?

Front-loaded with "One call:" and packed with useful detail in four sentences. The marketplace precedence chain is a dense pseudo-grammar and the parentheticals make it slightly run-on, but nothing is genuinely 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?

With no output schema, the description correctly enumerates the return fields (id, editToken, shopUrl, ownerUrl, parentUrl, kidUrl), which is exactly what an agent needs. The only gap is that childName's role and the interaction between count and explicit items are left unstated.

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?

At 50% schema coverage, the description compensates for several undocumented params (itemAsins, itemKeywords, ageBand/interests auto-fill semantics) and adds the marketplace precedence chain. However, childName is never explained in either place, and count's default/max is only restated from the schema.

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?

States a specific verb and resource — create a curated kids' Christmas gift wishlist — and names the distinguishing capability (one call instead of create_wishlist + add_wishlist_item). An agent can tell from the first sentence that this is the combined path rather than a step in it.

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?

"Preferred agent path" plus two concrete input modes (explicit ASINs/keywords/queries, or only ageBand/interests for auto-fill) give clear selection guidance. It does not state when to fall back to the granular siblings (create_wishlist then add_wishlist_item), which is the one missing exclusion.

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?