Skip to main content
Glama

Endorso

by com.endorso

endorso_cart

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesUp to 8 product queries or URLs, e.g. ["diapers size 3", "specialty coffee beans 1kg", "https://store.com/products/x"].
earnerNoYour stable earner id — commissions accrue to it. Required unless this MCP request authenticates as an Endorso partner.
countryNoISO-2 country for localized offers.
cashback_intentNoDefaults 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.

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