Skip to main content
Glama

Endorso

by com.endorso

endorso_monetize

Turn any product URL or free-text product query into a tracked, monetized affiliate link tied to your earner id. You earn a commission when someone buys through it. Pass cashback:true to check self-purchase cashback eligibility (honored only where the merchant network permits it — Amazon/AliExpress/Temu are excluded by their terms). If the product is not monetizable yet, a provisional tracked link is returned and merchant discovery is auto-enqueued.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesA product URL (https://…) or a free-text product query, e.g. "sony wh-1000xm5".
earnerNoYour stable earner/publisher id — commissions accrue to it. Optional; a random one is minted if omitted.
countryNoISO-2 country for localized offers, e.g. "US", "ES".
cashbackNoRequest self-cashback eligibility (earn on your own purchase where the network permits it).

TDQS

A4.3/5.0
Behavior4/5

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

The description details key behaviors: commission accrual, cashback eligibility limitations, provisional link generation for non-monetizable products, and auto-enqueued merchant discovery. No annotations exist to contradict, so the description carries the full transparency burden effectively.

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 concise with three sentences covering purpose, commission, cashback, and fallback behavior. It is front-loaded and avoids unnecessary detail.

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?

Given no output schema and four parameters, the description sufficiently explains what the tool does, its limitations, and special cases (e.g., provisional links). It is complete for an AI agent to use correctly.

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%, but the description adds meaningful context beyond schema: earner is optional with random minting, cashback includes merchant network restrictions. This enhances understanding without redundancy.

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 that the tool converts a product URL or free-text query into a tracked affiliate link tied to an earner ID, covering commission and cashback. It is distinct from sibling tools (balance, cart, search) which serve different purposes.

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?

The description provides clear usage context: any product URL or query can be used, and cashback eligibility is explained with specific exclusions (Amazon/AliExpress/Temu). It does not explicitly contrast with siblings but implicitly differentiates by purpose.

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

All Endorso 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

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: balance for financial info, cart for generating multi-store buying links, monetize for creating affiliate links, and search for product discovery. There is no overlap in functionality.

Naming Consistency5/5

All tools follow the consistent pattern 'endorso_<action/object>', using snake_case and a uniform prefix. The names clearly hint at the tool's function without ambiguity.

Tool Count4/5

4 tools is slightly below average but appropriate for a focused affiliate marketing server. It covers the essential workflows (search, monetize, cart, balance) without being overly sparse.

Completeness4/5

The tool set covers core affiliate actions: product search, link monetization, cart generation, and balance retrieval. Minor gaps exist, such as no dedicated tool for commission analytics or profile management, but agents can work around these.

Resources