A
licenseA
qualityC
maintenanceEnables AI assistants to recommend Amazon products with automatic affiliate link insertion, supporting product search, deals, bestsellers, and promotional content.
8
33
MIT
Endorso
by com.endorso
Server Details
Turn product links or queries into tracked links that can earn. Carts and search too.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
4 toolsendorso_balanceAInspect
Get your own authenticated earnings/cashback balance by currency: pending, approved, paid, plus recent commissions. Partner credentials read only their partner tag; signed-in users read only their account and claimed aliases.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| earner | No | Optional assertion of your own earner id. If supplied, it must match the authenticated owner. |
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read operation ('Get') and notes authentication constraints. However, it does not explicitly state whether the operation is non-destructive, require specific permissions, or mention 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 two concise sentences, front-loading the purpose and then adding scoping context. Every sentence adds value without redundancy.
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?
The tool has no output schema, so the description should explain the return values, but it only mentions what categories are included (pending, approved, paid, commissions) without specifying format structure or type. This is insufficient for a complete understanding.
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%; the schema already documents the optional 'earner' parameter with the same explanation. The tool description adds no new information about parameters, so baseline 3 applies.
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 retrieves the user's own earnings/cashback balance by currency, including pending, approved, paid, and recent commissions. This distinguishes it from sibling tools like endorso_cart (cart operations) and endorso_search (search).
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 explains scope differences between partner credentials and signed-in users, providing clear context on who can see what. It does not explicitly mention alternatives or when not to use, but the scoping is a strong guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
endorso_cartAInspect
Turn a shopping LIST (up to 8 free-text items or product URLs) into per-store buying links: Shopify and Amazon stores get a PRE-FILLED cart link the buyer lands on with everything added; other stores get deep product links. Carts default to own-purchase mode so network self-referral rules are applied. Set cashback_intent:false only when the earner is sharing the cart for someone else.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Up to 8 product queries or URLs, e.g. ["diapers size 3", "specialty coffee beans 1kg", "https://store.com/products/x"]. | |
| earner | No | Your stable earner id — commissions accrue to it. Required unless this MCP request authenticates as an Endorso partner. | |
| country | No | ISO-2 country for localized offers. | |
| cashback_intent | No | Defaults to true (own purchase). Set false only when sharing the cart for another buyer. |
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It covers the 8-item limit, store-specific link generation, and default mode. However, it omits authentication requirements (earner id vs partner), rate limits, error handling, and output format.
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?
Two sentences, front-loaded with the main purpose, no wasted words. Every sentence adds essential information about behavior and configuration.
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?
Given no output schema and moderate complexity, the description lacks specification of the output format (how buying links are returned). It also does not explain the earner authentication path beyond the schema description.
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% with descriptions for all 4 parameters. The description adds meaningful context beyond the schema: the 8-item limit for 'items' and the purpose of 'cashback_intent' (own purchase vs sharing).
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 transforms a shopping list into per-store buying links, specifying differentiation for Shopify/Amazon vs other stores. It distinguishes from sibling tools (balance, monetize, search) by focusing on cart creation.
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 context for using cashback_intent:false when sharing a cart, but does not explicitly say when to use this tool versus alternatives or give exclusions. The own-purchase default and network self-referral rules are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
endorso_monetizeAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | A product URL (https://…) or a free-text product query, e.g. "sony wh-1000xm5". | |
| earner | No | Your stable earner/publisher id — commissions accrue to it. Optional; a random one is minted if omitted. | |
| country | No | ISO-2 country for localized offers, e.g. "US", "ES". | |
| cashback | No | Request 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.
endorso_searchAInspect
Search real, currently-buyable products across the web and affiliate catalogs. Returns offers with merchant, price, url, and whether each is monetizable. Use to pick a specific offer before endorso_monetize.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What to search for. | |
| country | No | ISO-2 country code. |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that results include merchant, price, url, and monetizable flag, but lacks details on side effects, rate limits, pagination, or authentication needs.
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?
Two sentences, front-loaded, zero wasted words. Every sentence adds value: first defines the action, second specifies return fields and usage context.
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 the simple parameter set (2 params, no enums, no output schema), the description adequately covers what the tool does, what it returns, and how to integrate it with a sibling tool. Minor gaps (result limits, error handling) are acceptable for a straightforward search tool.
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% (both params have descriptions). The overall description adds context about the search scope and return type but does not enhance understanding of the individual parameters 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 states 'Search real, currently-buyable products across the web and affiliate catalogs' with specific verb and resource, and distinguishes from siblings (balance, cart, monetize) by noting it is used to pick an offer before endorso_monetize.
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 explicitly says 'Use to pick a specific offer before endorso_monetize', providing clear context and a recommended workflow, but does not state when not to use it or mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
4 tool updates
- First observed
endorso_balance - First observed
endorso_cart - First observed
endorso_monetize - First observed
endorso_search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Create geo-targeted affiliate smart links, pull analytics, and rewrite YouTube descriptions.
AI-powered product search, affiliate links, and price negotiation for e-commerce platforms
Create and manage short links, track clicks, and automate URL management
Generate Amazon affiliate sales funnels from product URLs. AI-powered, free.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search products and generate affiliate links across European and global affiliate networks, automating product discovery and link creation for monetization.25MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to search products across affiliate networks, compare commissions, find arbitrage opportunities, and get auto-injected affiliate links via MCP.-
- AlicenseNot gradedqualityCmaintenanceEnables affiliate marketing and product promotion across Taobao, JD.com, and Pinduoduo platforms with link conversion, product search, and order tracking capabilities.68117ISC
Try in Browser
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.