Skip to main content
Glama

Mother's Day Gifts – hand-picked gift ideas

One-shot create and fill

create_and_fill

One call: create a curated Mother's Day (Mors dag) gift wishlist and return shopUrl (share link) + ownerUrl. Preferred agent path: create a Mother's Day wishlist and add ASINs / keywords / search queries in one call. Returns id, editToken, ownerUrl, shopUrl. OpenAPI: agentCreateAndFill.

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_and_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
itemAsinsNo
styleTagsNo
budgetBandNo
itemQueriesNoEach query is searched and added as a wish
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.
itemKeywordsNo
relationshipNo
recipientNameNo

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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true. The description adds genuine behavioral context: it performs search-and-add side effects for `itemQueries`, produces a public share link (shopUrl) plus an editToken-bearing ownerUrl, and lists exactly which identifiers come back. It omits idempotency — whether a second call creates a duplicate wishlist — which matters for a one-shot creator.

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 is front-loaded, but the return values are stated twice ("return shopUrl (share link) + ownerUrl" then "Returns id, editToken, ownerUrl, shopUrl"), and "OpenAPI: agentCreateAndFill" is an internal artifact the agent cannot act on.

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?

No output schema exists, so listing return identifiers is necessary and done. But with 10 all-optional parameters, zero required, and no documented defaults or combination guidance (e.g. ASINs vs queries vs keywords), an agent still has to guess how to compose a first 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?

At 30% schema coverage the description must carry the load, and it partly does by mapping its main inputs to roles: ASINs, keywords, and search queries are the three fill modes. It says nothing about styleTags, budgetBand, relationship, recipientName, or locale/occasion semantics, leaving half the surface dependent on bare schema.

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 ("create a curated Mother's Day gift wishlist") plus its composite nature (adds ASINs/keywords/queries in one call). The "one-shot" framing distinguishes it from the slower create_wishlist + add_wishlist_item path, though it never names those siblings explicitly.

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?

"Preferred agent path" gives a directional signal that this beats the multi-call flow, and the description scopes usage to Mother's Day. But no sibling is named as the alternative and no when-not-to-use is given. The Mother's Day-only framing also sits awkwardly against the schema's `occasion` enum (birthday, just-because, other).

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