Skip to main content
Glama

Valentine's Day Gifts – hand-picked gift ideas

Resolve buy / inspiration link

resolve_product
Read-only

Resolve an ASIN, pasted Amazon /dp/ URL, or keywords to a buyUrl (product /dp or romantic search). Pass marketplace=amazon.com for US shoppers or amazon.se for Sweden (fallback: country, then Accept-Language en-US → amazon.com, else amazon.se). Uses the server's tracking ID for each storefront; never invents tags. 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-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).
categoryNo
keywordsNoSearch keywords if no ASIN
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.
preferSearchNo

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
    • 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?

With readOnlyHint and openWorldHint already present, the description adds useful behavior: it uses the server's tracking ID per storefront, never invents tags, and states that a missing store never errors. It does not cover auth or rate limits, but it adds meaningful context beyond annotations.

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 description is front-loaded with the core purpose and remains reasonably short. The dense marketplace parenthetical and the trailing 'OpenAPI: resolveProduct' add some redundancy but do not obscure the main instruction.

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?

It covers the central resolution behavior and marketplace fallback, which is the most important context. For a tool with 9 optional parameters and no output schema, however, it omits enough parameter behavior that an agent could still be unsure about preferSearch, category, and occasion.

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?

The description explains the marketplace fallback chain, but most of that detail is already present in the schema's marketplace description. It leaves preferSearch, category, and occasion behavior unexplained, so it adds limited semantic value over the 67%-covered 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?

The description states a specific verb and inputs/output: resolve an ASIN, pasted Amazon /dp/ URL, or keywords to a buyUrl. It is clear, but it does not explicitly differentiate the tool from siblings such as search_gifts or get_catalog.

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 usage by listing accepted inputs and gives marketplace selection guidance for US vs Sweden. However, it does not explicitly say when to choose this tool over siblings or when not to use it.

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