Skip to main content
Glama

Mother's Day Gifts – hand-picked gift ideas

Resolve buy link

resolve_product
Read-only

Resolve an ASIN, pasted Amazon /dp/ URL, or keywords to a buyUrl (product /dp or Mother's Day search). Pass marketplace + locale (marketplace=amazon.com for US/English, amazon.se for Sweden; if omitted, Accept-Language en-US → amazon.com, else amazon.se). OpenAPI: resolveProduct.

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": "resolve_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPasted Amazon product URL
asinNo10-char Amazon ASIN
localeNoUser locale, e.g. en, sv, de, fr, es (mothers day / mors dag / Muttertag / fête des mères / día de la madre)
keywordsNoSearch keywords if no ASIN
occasionNo
styleTagNo
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.
preferSearchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the Accept-Language en-US → amazon.com / otherwise amazon.se resolution default, and the fact that non-US/SE storefronts fall back to Mother's Day search links. That fallback behavior is exactly the kind of transparency an agent needs.

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 main behavior (what it resolves to) is front-loaded in the first clause, and the marketplace guidance follows logically. The text is dense but mostly earns its place; the trailing 'OpenAPI: resolveProduct.' and some redundant marketplace restatement add minor noise.

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?

For a 9-parameter, zero-required tool with no output schema, the description covers the resolution logic and the two most consequential parameters well. But four enum parameters (occasion, styleTag, budgetBand, preferSearch) and the semantics of combining them are undocumented, so an agent has to guess how input shapes the returned buyUrl.

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 coverage is moderate (56%). The description meaningfully documents marketplace and locale defaults and ties url/asin/keywords to the input types, adding value beyond the schema. However, occasion, styleTag, budgetBand, and preferSearch receive no explanation in either the description or the schema, leaving several enum parameters semantically opaque.

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?

The description states a specific verb and resource: 'Resolve an ASIN, pasted Amazon /dp/ URL, or keywords to a buyUrl'. It also specifies the two output shapes (product /dp or Mother's Day search), so an agent can tell what it produces. It stops short of explicitly distinguishing itself from a keyword-overlapping sibling such as search_gifts.

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 gives clear guidance for one decision (when to pass marketplace=amazon.com vs amazon.se, and the behavior when omitted). But it never says when to use this tool instead of siblings like search_gifts or get_catalog, and the roles of preferSearch, occasion, and styleTag in selecting this tool are left entirely implicit.

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