Skip to main content
Glama

AgentIQ

by io.github.chrisgu

mint_amazon_affiliate_link

[Sell/Shared] Mint an Amazon Associates affiliate URL for MoltAd. Pass any amazon.com product/search URL — adds/replaces tag=. SiteStripe short links (amzn.to / a.co) pass through unchanged (tracking already embedded). Optional wrapTracked=true mints a MoltAd /r hop on moltadserver.com. Always surface the returned disclosure to end users. Also: GET/POST /api/public/amazon-affiliate-link. PA-API product search is a follow-up; tag rewrite is enough to earn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAmazon product, search, or amzn.to / a.co URL (https).
originNoOptional origin hint for the tracked hop (publisher page URL).
wrapTrackedNoWhen true, also wrap the tagged Amazon URL in a MoltAd tracked hop (moltadserver.com/r/...). Default false.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses exactly what happens: tag addition/replacement, short-link pass-through, optional MoltAd hop wrapping, and the requirement to surface the returned disclosure. It even mentions the REST endpoint and product-search follow-up, leaving little hidden behavior.

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?

Every sentence earns its place: purpose, transformation rule, short-link exception, optional wrapping, disclosure obligation, and roadmap. The main purpose is front-loaded and the prose is compact without being under-specified.

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?

For a simple 3-parameter transform with no output schema, the description covers invocation semantics, edge cases, and a compliance requirement. The only notable gap is the exact return shape beyond 'the returned disclosure,' which an agent would need to discover at runtime but does not block correct invocation.

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 100%, so the baseline is 3, but the description adds meaningful context: url accepts product/search/short-link forms, short links pass through unchanged, and wrapTracked=true adds a MoltAd hop. The origin parameter remains schema-only, but the overall added value justifies a 4.

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 opens with a specific verb-resource pair: 'Mint an Amazon Associates affiliate URL for MoltAd.' It immediately explains the core mechanism (adds/replaces tag=...) and is clearly distinct from all sibling tools, none of which mint affiliate links.

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 gives clear context on valid inputs: any amazon.com product/search URL qualifies, SiteStripe short links pass through unchanged, and wrapTracked=true changes behavior. It does not explicitly name alternative tools or exclusions, but the PA-API follow-up remark signals this is the intended tool for immediate tag-rewrite earning.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentIQ toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

Multiple tools have overlapping or misleading purposes: buy_campaign and buy_placement are aliases of create_campaign, list_placement actually creates a placement, and get_attribution/get_campaign both provide campaign stats. The report_* tools are distinct but similarly named, increasing selection risk.

Naming Consistency3/5

Most tools follow a verb_noun snake_case pattern, but there are notable deviations: buy_campaign/buy_placement use 'buy' instead of 'create', list_placement is a creator not a lister, and simple nouns like 'wallet' and 'whoami' break the convention.

Tool Count2/5

At 31 tools, the server feels heavy. Several tools are redundant aliases (buy_campaign, buy_placement) or could be consolidated (multiple report_* and list_* variants), making the surface unnecessarily large for the ad marketplace domain.

Completeness3/5

The core lifecycle is covered: campaign/placement creation, delivery, reporting, attribution, refunds, and cashouts. However, there are gaps like no update_campaign, no true list_placements, and no get_placement, leaving some workflows incomplete.

Resources