Skip to main content
Glama
heikowagner

Amazon Affiliate MCP Server

by heikowagner

amazon_gift_finder

Generate tailored Amazon gift links with affiliate tags for any country, using recipient details, interests, budget, and occasion, including a gift card fallback option.

Instructions

Generate personalized Amazon gift idea links with affiliate tags for any country. Tailors search links based on recipient description, interests, budget range, and occasion. Always includes an Amazon gift card as a reliable fallback option.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anlassNoOccasion for the gift, e.g. Birthday, Christmas, Wedding
countryNoAmazon storefront country code. Default: dede
budget_maxNoMaximum budget in the local currency of the selected country
budget_minNoMinimum budget in the local currency of the selected country
empfaengerYesDescription of the gift recipient, e.g. 'man 40, loves sports' or 'teenage girl into gaming'
interessenNoList of interests or hobbies, e.g. ['gaming', 'cooking', 'reading'] (max 5)
Behavior3/5

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

With no annotations provided, the description does carry the burden. It discloses key behaviors: incorporating affiliate tags, creating search links, and always including a gift card as fallback. Still, it does not mention output format, potential limitations, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is three sentences long, front-loaded with the core purpose, and each sentence adds valuable context (country coverage, tailoring factors, gift card fallback). No unnecessary words.

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?

Without an output schema, the description should clarify what the tool returns. It mentions 'gift idea links' but does not specify the exact return format (e.g., array of URLs, text, structured data). It adequately conveys the core function but leaves some ambiguity.

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 description coverage is 100%, so the baseline is 3. The description mentions the relevant parameters (recipient, interests, budget, occasion) but adds no new semantics beyond what the schema already provides.

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?

The description clearly states the tool's function: generating personalized Amazon gift idea links with affiliate tags. It distinguishes itself from sibling tools like amazon_search or amazon_deals by focusing on personalized gift recommendations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It indicates when to use the tool (when personalized gift ideas are needed) and describes tailoring by recipient description, interests, budget, and occasion. However, it does not explicitly exclude alternatives or mention 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heikowagner/amazon-affiliate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server