Affilio Link Tools

Auth.List Links

auth.list_links

List affiliate links in your Affilio account with pagination.

Returns an array of link objects sorted by creation date (newest first). Each item includes: ID, short URL, title, target URL, labels, affiliate classification, archive status, visibility, and click count.

Use skip + limit to paginate through large link collections. 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 per page (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 links by project ID (MongoDB ObjectId string). If omitted, returns 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 per page (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 links by project ID (MongoDB ObjectId string). If omitted, returns 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.5/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 and does well: it states the return type (array), sort order, which fields are included, pagination behavior, and Bearer token authentication. It does not cover failure modes or rate limits, but the disclosed behavior is substantially beyond the bare tool name.

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 compact and well structured: purpose, return details, pagination usage, and authentication are each covered in separate concise sentences. The technical reference link is the only nonessential element, but it does not bloat the text.

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?

For a simple paginated list tool with two optional parameters and an output schema, the description is complete: it explains what the tool lists, how results are ordered, what each item includes, how to paginate, and the auth requirement. Nothing critical is missing for an agent to invoke it 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% and both parameters already have clear descriptions and bounds. The description adds a small but useful semantic layer by explicitly connecting skip and limit to paginating through large link collections, reinforcing the intended usage beyond 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 opens with a specific verb and resource ('List affiliate links in your Affilio account') and clarifies it returns paginated results sorted by creation date, newest first. This distinguishes it from the sibling list_links_ranked by noting the sort order, and from get_link by indicating it lists many items.

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?

It clearly instructs to use skip + limit for pagination, which is direct usage guidance for this tool. The when-to-use is implied by the list-focused purpose, but it does not explicitly contrast this with siblings such as list_links_ranked or get_link, so one minor exclusion is missing.

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?