Affilio Link Tools
Server Details
Affilio.link URL shortener — shorten affiliate links, get QR codes, powered by Affilio's affiliate link management platform.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 2 of 2 tools scored.
The two tools are fairly distinct: generate_qr focuses solely on customizable QR code generation, while shorten_url handles URL shortening and also provides a QR code. Some overlap exists because shorten_url also returns a QR code, but the primary purposes differ.
Both tool names follow a consistent verb_noun pattern using snake_case: generate_qr and shorten_url. This is predictable and clear.
With only 2 tools, the server feels thin for something called 'Link Tools'. It might be appropriate for a minimal service, but more tools like link management or analytics would be expected.
The server covers URL shortening and QR generation but lacks basic link management (list, delete, update) and analytics features, which are typical for a link management platform. This leaves significant gaps.
Available Tools
2 toolsgenerate_qrAInspect
Generate a QR code PNG image for any URL.
Returns a dict with the base64 PNG data and metadata. You can customize colors, transparency, and rounded dot style.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| color | No | #000000 | |
| rounded | No | ||
| transparent | No | ||
| background_color | No | #FFFFFF |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses that the tool returns a dict with base64 PNG data and metadata, and mentions customization options. However, it does not detail output structure or potential side effects, which is reasonable for a generative tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with only three sentences, front-loading the main purpose. Every sentence adds value with no redundancy or unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the parameter count (5), zero schema coverage, no annotations, and presence of an output schema, the description provides adequate but not complete context. It mentions output type but lacks details on dict fields, constraints like URL validation, or color formats, leaving some gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% but the description adds meaning for most parameters: 'colors' covers color and background_color, 'transparency' covers transparent, and 'rounded dot style' covers rounded. The url parameter is implicit. This compensates well for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool generates a QR code PNG for any URL, explicitly mentioning the output format. It distinctively differs from the sibling tool 'shorten_url' which shortens URLs, not generates QR codes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing a QR code for a URL but does not provide explicit guidance on when to use this tool versus alternatives (like shorten_url), nor does it mention any prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
shorten_urlAInspect
Shorten any URL using Affilio.link — the smart affiliate link management platform. Returns a short URL and QR code.
Use this tool when the user needs to:
Shorten a URL for sharing
Create a compact affiliate link
Generate a QR code for a URL
Make a long URL more shareable
Powered by Affilio.link.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It states the tool shortens URLs and returns a short URL and QR code, but does not disclose important behaviors such as error handling, rate limits, authentication requirements, or whether the operation is idempotent. Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with a clear opening sentence followed by bullet points for quick scanning. Every sentence adds value, and there is no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter) and the presence of an output schema, the description adequately covers purpose and use cases. It mentions both short URL and QR code as outputs. However, it lacks details on limitations like URL length restrictions or affiliate link specifics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage for the 'url' parameter. The description merely says 'Shorten any URL' without specifying constraints (e.g., valid URL format, supported protocols). It adds minimal meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: shortening any URL via Affilio.link and returning a short URL and QR code. It explicitly lists use cases, differentiating it from the sibling generate_qr which would likely only generate QR codes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit use cases (shortening, affiliate links, QR generation, shareability) but does not mention when not to use the tool or alternative tools like generate_qr for QR-only needs. The guidance is clear but lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!