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–100). Default: 50.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 8, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of links to return per page (1–200). Default: 50."New value: +"Maximum number of links to return per page (1–100). Default: 50."

changedInput schema / properties / limit / maximum
```
Previous value: -200New value: +100
```

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.2/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 burden of behavioral disclosure. It states the Bearer token authentication requirement, return order (newest first), and pagination behavior. It implies a read-only operation though not explicitly stated, and doesn't mention rate limits or potential errors, but covers the essential behavioral traits.

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?

Five clear sentences, front-loaded with the purpose, then return details, pagination guidance, and auth requirement. No redundancy, and every sentence earns its place.

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 low complexity, presence of an output schema, and full param schema, the description covers purpose, return summary, auth, and pagination. It lacks explicit alternatives but includes a technical reference link, making it complete enough for confident usage.

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 schema already fully describes both skip and limit parameters (100% coverage). The description adds only a pagination usage hint without new semantic details, so it meets the baseline for a well-covered schema without adding extra meaning.

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 verb 'list', the resource 'affiliate links', and scope 'in your Affilio account'. It also mentions pagination, which distinguishes it from single-link retrieval tools like auth.get_link and ranked list auth.list_links_ranked.

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 advises using skip and limit for pagination in large collections, giving explicit usage context. However, it doesn't explicitly contrast with sibling tools like list_links_ranked, so it's clear but not fully differentiated in terms of when-not-to-use.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?