Skip to main content
Glama

Mother's Day Gifts – hand-picked gift ideas

Create Mother's Day gift list

create_wishlist

Create a Mother's Day gift wishlist. Returns id, editToken, ownerUrl, shopUrl, wishlist, storage. Save editToken for add_wishlist_item. If storage is token, later mutations may return a new id — always use the latest. OpenAPI: createWishlist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
localeNoUser locale, e.g. en, sv, de, fr, es (mothers day / mors dag / Muttertag / fête des mères / día de la madre)
occasionNo
styleTagsNo
budgetBandNo
marketplaceNoAmazon storefront for the end user, e.g. amazon.se, amazon.com, us, se, de. Recommended: pass marketplace=amazon.com for US shoppers (US catalog, English, USD, tag sw-mothersday-20) and amazon.se for Sweden (SE catalog, tag sw-mothersday-21). If omitted: Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get Mother's Day search links.
relationshipNomom | stepmom | mother-in-law | grandma | other
recipientNameNoMom / recipient display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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 Mother's Day search deep-links."New value: +"Amazon storefront for the end user, e.g. amazon.se, amazon.com, us, se, de. Recommended: pass marketplace=amazon.com for US shoppers (US catalog, English, USD, tag sw-mothersday-20) and amazon.se for Sweden (SE catalog, tag sw-mothersday-21). If omitted: Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get Mother's Day search links."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare non-readOnly and openWorld; the description adds real behavioral context the agent can't get elsewhere: the exact return fields, that editToken must be retained for later mutation, and the non-obvious caveat that storage=token causes later mutations to return a new id. It omits permission/auth requirements and error behavior, keeping it below 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.

Conciseness4/5

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

Front-loaded with purpose, then return shape, then the token/id caveat — a sensible priority order with no filler sentences. 'OpenAPI: createWishlist.' is spec bookkeeping that adds little for an agent, a minor waste.

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?

With 8 parameters, no output schema, and an open-world mutation, the description usefully enumerates return fields and the token/id stability rule. But it leaves the items array and its per-item shape, plus the effect of occasion/styleTags/budgetBand on the generated list, entirely to the schema — an agent forming a first call has real gaps.

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

Parameters2/5

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

Schema coverage is only 50%, so the description should carry weight for the undocumented parameters, yet it says nothing about items, occasion, styleTags, or budgetBand. The richest parameter documentation (locale, marketplace, relationship, recipientName) lives entirely in the schema, so the description adds no semantic meaning to any input.

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?

Specific verb + resource: 'Create a Mother's Day gift wishlist.' An agent can tell this is a creation operation distinct from get_wishlist or add_wishlist_item. It doesn't distinguish itself from the sibling create_and_fill, which appears to be a create-and-populate variant, so it falls short of a 5.

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?

It implies downstream usage ('Save editToken for add_wishlist_item'), which signals a create-then-populate workflow, but never states when to choose this over create_and_fill or when an agent should skip creating a list entirely. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources