Affilio Link Tools

Auth.List Links Ranked

auth.list_links_ranked

List affiliate links ranked by click performance (highest click count first).

Returns the same link schema as auth.list_links but ordered by total clicks descending. Useful for identifying your top-performing affiliate links, optimising content strategy, and spotting underperforming links that need attention.

Use skip + limit to paginate. Requires Bearer token authentication.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skip`	No	Number of links to skip for pagination. Default: 0.
`limit`	No	Maximum number of links to return (1–200). Default: 50.

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.

Changed1 schema field changedJul 9, 2026

removedInput schema / properties / project_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Filter to a specific project ID (MongoDB ObjectId string). If omitted, ranks links across all projects in the account."
-}

Changed6 schema fields changedJun 26, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of links to return (1–200). Default: 50."
```
- addedInput schema / properties / limit / maximum
```
Added value: +200
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / project_id / description
```
Added value: +"Filter to a specific project ID (MongoDB ObjectId string). If omitted, ranks links across all projects in the account."
```
- addedInput schema / properties / skip / description
```
Added value: +"Number of links to skip for pagination. Default: 0."
```
- addedInput schema / properties / skip / minimum
```
Added value: +0
```
AddedJun 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral disclosure burden. It clearly discloses the ordering behavior, pagination via skip/limit, and the authentication requirement. It does not explicitly state that this is a read-only operation or mention rate limits, but the behavioral traits most relevant for invoking it are present.

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 and front-loaded with the primary purpose and ordering behavior. The use-case sentence and technical reference are useful but not strictly necessary, making it slightly longer than the minimum. Still, every sentence contributes meaning and there is no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only two simple optional parameters and an output schema, the description is complete. It covers what the tool returns, how results are ordered, how to paginate, why it is useful, and what authentication is required. An agent has enough information to invoke it correctly without inspecting additional metadata.

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 skip and limit are already fully documented with defaults and constraints. The description adds value by explicitly tying the two parameters together as the pagination mechanism and clarifying the ordering context in which pagination applies. This goes slightly beyond simply restating the schema.

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 lists affiliate links and explicitly defines the ranking behavior: highest click count first. It also differentiates itself from auth.list_links by noting it returns the same schema but ordered by total clicks descending. This makes it easy for an agent to distinguish from sibling tools.

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 gives concrete use cases: identifying top performers, optimizing content strategy, and spotting underperforming links. It also references auth.list_links as the base schema, implying the difference between the two. It stops short of explicitly stating when NOT to use this tool, but the ranking context is clear enough.

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?