Affilio Link Tools

Auth.Get Link Stats

auth.get_link_stats

Retrieve click analytics for a specific affiliate link.

Returns aggregated traffic data for the link: total clicks, unique visitor estimates, geographic breakdown, referrer sources, and device/browser distribution (data availability depends on the analytics backend configuration).

Requires Bearer token authentication.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "link_id": "<link_id>"
    },
    "name": "auth.get_link_stats"
  }
}

Input Schema

Name	Required	Description	Default
`link_id`	Yes	Link ID returned by auth.create_link or auth.list_links.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 9, 2026

changedInput schema / properties / link_id / description

Previous value: -"Unique link ID (MongoDB ObjectId string) of the link whose click statistics to retrieve. Retrieve link IDs via auth.list_links or auth.create_link."New value: +"Link ID returned by auth.create_link or auth.list_links."

Changed1 schema field changedJun 26, 2026

addedInput schema / properties / link_id / description

Added value: +"Unique link ID (MongoDB ObjectId string) of the link whose click statistics to retrieve. Retrieve link IDs via auth.list_links or auth.create_link."

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, the description carries the behavioral disclosure burden. It explicitly states the Bearer token requirement and flags that data availability depends on analytics backend configuration, which is a meaningful limitation. It does not discuss rate limits or error behavior, but the get/retrieve semantics and output schema cover most remaining operational concerns.

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 definition is compact: purpose, return composition with caveat, and auth requirement are stated in three substantive sentences followed by a short reference URL. It is front-loaded and free of filler, though the external reference line is optional.

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 one-parameter read-only analytics tool with an output schema, the description covers submission context (link_id), authentication, and the limits of data availability. It might be improved by stating behavior for invalid or zero-click links, but the output schema and existing caveat make it sufficiently complete for selection and invocation.

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 single parameter is fully documented in the input schema ('Link ID returned by auth.create_link or auth.list_links'), so schema coverage is 100%. The description only refers to 'a specific affiliate link' and adds no semantic detail beyond the schema, so baseline 3 is appropriate.

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?

The description opens with the specific verb 'Retrieve' and the resource 'click analytics for a specific affiliate link,' then lists the aggregated traffic dimensions returned. It is clearly distinct from siblings like auth.get_link, which would return link record data rather than analytics, although it never names or contrasts those siblings explicitly.

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 first sentence establishes the intended use: fetch click analytics for one link, and the 'specific' wording rules out bulk or comparative reporting. No alternative tool is named and no when-not-to-use conditions are given, so the guidance is clear context without exclusions.

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?