Skip to main content
Glama

Valentine's Day Gifts – hand-picked gift ideas

Search Valentine gifts

search_gifts
Read-only

Search Amazon for Valentine's / romantic gift ideas on the user's marketplace. Returns PA-API products when configured for the default storefront, otherwise romantic-filtered search deep-link cards + catalogMatches. Prefer buyUrl / trackingTag in results. Pass marketplace=amazon.com for US shoppers (amazon.com/dp links, English) or amazon.se for Sweden; without it, country, then Accept-Language en-US → amazon.com, else amazon.se. OpenAPI: searchAmazon.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_gifts"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query, e.g. heart necklace
limitNo
localeNoUser locale, e.g. en-US, en, sv. amazon.com always answers in English.
countryNoISO country of the shopper, e.g. US or SE. Used when marketplace is omitted (US → amazon.com).
interestNoGift category filter
occasionNo
marketplaceNoAmazon storefront for the end user: amazon.com (United States) or amazon.se (Sweden, default); ids like us/se also work. Pass marketplace=amazon.com for US shoppers to get amazon.com/dp/ASIN links with English titles. If omitted, country is used, then Accept-Language (en-US → amazon.com), else amazon.se. A missing store never errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country of the shopper, e.g. US or SE. Used when marketplace is omitted (US → amazon.com).",
      +  "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, en, sv. amazon.com always answers in English."
    • 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 produce /dp links on amazon.se and amazon.com (US); other marketplaces get romantic search deep-links."New value: +"Amazon storefront for the end user: amazon.com (United States) or amazon.se (Sweden, default); ids like us/se also work. Pass marketplace=amazon.com for US shoppers to get amazon.com/dp/ASIN links with English titles. If omitted, country is used, then Accept-Language (en-US → amazon.com), else amazon.se. A missing store never errors."
    • removedInput schema / properties / marketplace / minLength
      Removed value: -2
    • changedInput schema / required
      Previous value: -[
      -  "q",
      -  "marketplace",
      -  "locale"
      -]New value: +[
      +  "q"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, yet the description adds real substance: two distinct result modes (PA-API products when configured vs. deep-link cards + catalogMatches otherwise) and the reassuring 'a missing store never errors' degradation rule. It stops short of describing pagination or the card payload shape.

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 lead sentence and result-mode note are well front-loaded, but the marketplace fallback chain is restated almost verbatim from the schema description, which adds length without new information. The final 'OpenAPI: searchAmazon' reference is a useful pointer, but overall density is high and slightly repetitive.

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 does the right thing by sketching the return forms (PA-API products vs. deep-link cards with catalogMatches) and highlighting buyUrl/trackingTag. For a 7-parameter search tool, missing coverage of limit and the occasion semantics keeps it just short of complete.

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 71%, and the description goes further by spelling out the marketplace→country→Accept-Language resolution order and locale effects (amazon.com answers in English). It adds meaning beyond the schema for marketplace/country/locale, though it says nothing about limit or the occasion enum values.

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 — searching Amazon for Valentine's/romantic gifts on the user's marketplace — and pins down the scope (gift search, not catalog lookup or wishlist manipulation), which separates it from siblings like get_catalog, resolve_product, and add_wishlist_item.

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?

Offers useful routing guidance for the marketplace parameter (pass amazon.com for US shoppers, amazon.se for Sweden, with a clear fallback chain) and advises preferring buyUrl/trackingTag in results. However, it never says when to choose this over sibling tools such as get_catalog or resolve_product, so tool selection is only implied.

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