Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_check_link_health

Read-onlyIdempotent

Trigger a health check for a specific smart link.

    Checks the default URL and all geo-rule URLs for availability.
    Returns the health status (healthy/broken/unknown).
    Rate limited to once per 5 minutes per link.
    Does NOT modify the link configuration.

    Common errors:
    - Rate limit: wait 5 minutes between health checks for the same link.
    - Smart link not found: check the ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description adds valuable behavior: it checks all geo-rule URLs, returns health status, is rate limited, and explicitly states 'Does NOT modify the link configuration.' This substantially enriches the annotation-provided safety profile.

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 well-structured with the primary action first, followed by bullet-like lines for scope, return, rate limit, and non-modification. It then lists common errors. Every sentence adds value, and there is no unnecessary verbosity.

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 the tool's simplicity, the presence of an output schema, and strong annotations, the description covers all necessary context: what URLs are checked, rate limiting, errors, and the non-mutating nature. It is complete for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the id or response_format parameters at all, and schema description coverage is 0%. Although the input schema itself has descriptions, the rule for low coverage requires the description to compensate, which it fails to do. The agent must rely entirely on the schema for parameter 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 action: 'Trigger a health check for a specific smart link.' This specifies the verb (trigger) and resource (smart link health check), and it distinguishes the tool from siblings like get_smart_link or update_smart_link by focusing on health checking.

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 provides clear usage context: it checks default and geo-rule URLs, is rate limited to once per 5 minutes, and does not modify configuration. It also lists common errors. However, it does not explicitly name alternative tools for when not to use it, so it stops short of a perfect 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Youfiliate Smart Links toolsInspect
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

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource or action, from smart link CRUD to health checks, statistics, and YouTube migration lifecycle. There is no meaningful overlap; even similar-sounding tools like get_smart_link and get_smart_link_stats are clearly separated by configuration vs. detailed analytics.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with a uniform 'youfiliate_' prefix, e.g., create_smart_link, get_smart_link, delete_smart_link, and start_migration. No mixed conventions or exceptions are present.

Tool Count4/5

With 18 tools, the set is slightly larger than the ideal 3-15 range but remains well-scoped for the dual domain of smart link management and YouTube migration. Each tool has a clear purpose, and the count is not excessive given the feature coverage.

Completeness5/5

The tool surface covers the full smart link lifecycle (create, read, update, delete, list) plus advanced features like health checks, aggregate/per-link stats, and preferences. The YouTube migration workflow is also complete with connect/disconnect, status, preview, start, list, status, and rollback, leaving no obvious dead ends.

Resources