Affilio Link Tools

Auth.Search Products

auth.search_products

Search for products on a connected affiliate platform.

Returns live product listings from the platform's catalog including: product name, price, image URL, direct affiliate link, ASIN/item ID, and platform metadata. Results are ready to pass directly to auth.create_product.

Prerequisites:

Platform integration must be active (connect via Affilio dashboard → Settings → Integrations)
Verify with auth.list_integrations before calling

Error envelopes:

plan_restriction: Live product search requires a paid Affilio plan
validation_error: Unsupported or misspelled platform name
no_integrations_connected: No integration found for the requested platform
auth_error: Missing or invalid Bearer token

Requires Bearer token authentication.

Technical reference: https://affilio.link/blog/mcp-for-everyone

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of products to return (1–50). Default: 10.
`query`	Yes	Product search query sent to the affiliate platform's live catalog. Use natural-language product descriptions for best results. Example: 'wireless noise cancelling headphones', 'standing desk electric'.
`platform`	Yes	Affiliate platform to search. Supported values: amazon, aliexpress, ebay. The corresponding platform integration must be connected in your Affilio account (Settings → Integrations). Check auth.list_integrations to verify connectivity.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedJun 26, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of products to return (1–50). Default: 10."

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / platform / description

Added value: +"Affiliate platform to search. Supported values: amazon, aliexpress, ebay. The corresponding platform integration must be connected in your Affilio account (Settings → Integrations). Check auth.list_integrations to verify connectivity."

addedInput schema / properties / query / description

Added value: +"Product search query sent to the affiliate platform's live catalog. Use natural-language product descriptions for best results. Example: 'wireless noise cancelling headphones', 'standing desk electric'."

AddedJun 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that results are live, requires Bearer token authentication, lists prerequisites, and enumerates relevant error envelopes such as plan_restriction and no_integrations_connected. It stops short of explicitly stating read-only semantics, but 'search' and 'returns listings' strongly imply no mutation.

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 well structured: a one-sentence purpose, a concise returns summary, prerequisites, and error envelopes. It is slightly longer than strictly necessary due to the technical reference link and repeated platform examples, but the organization helps an agent parse requirements quickly.

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 search tool with an output schema and richly described parameters, the description covers the necessary context: prerequisites, authentication, error behavior, and the downstream use of results. It does not mention rate limits or explicit read-only guarantees, but these are not blocking for an agent to invoke the tool correctly.

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?

The input schema already documents all three parameters with 100% coverage, including defaults, limits, supported values, and examples. The description adds no significant parameter-level meaning beyond what the schema provides, such as how limit interacts with pagination or how platform values map to integrations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search for products on a connected affiliate platform' and clarifies it returns live catalog listings with product details. The description differentiates from nearby tools like list_store_products by emphasizing the live external platform catalog and integration prerequisite, though it does not explicitly name sibling alternatives.

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?

Provides clear usage context: requires an active platform integration, advises verifying with auth.list_integrations, and notes results are ready for auth.create_product. It does not explicitly state when not to use the tool or name a specific alternative, but the integration prerequisite and 'live affiliate platform' framing make the intended scenario clear.

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

All Affilio Link Tools tools Inspect

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

A3.9/5.0

Disambiguation4/5

Most tools map cleanly to distinct resources and actions, but auth.create_link vs shorten_url and check_url vs check_international_redirect have overlapping purposes. The descriptions do a good job of clarifying the differences, so ambiguity is limited.

Naming Consistency4/5

All names follow a readable snake_case verb_noun pattern, but auth.* tools are prefixed while utility tools like check_url, generate_qr, and shorten_url are not. Names like list_links and list_links_ranked are also close, though still predictable.

Tool Count3/5

20 tools is on the heavy side for this domain. Most cover distinct functions, but there is some redundancy such as list_links_ranked being a sorting variant of list_links and shorten_url overlapping with auth.create_link.

Completeness3/5

Link lifecycle coverage is solid: create, get, list, update, archive, stats, and visibility are all present. However, product management is incomplete with no update/delete/remove-link operations, and there is no unarchive or hard-delete for links.

Resources

Need Help?