Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_create_smart_link

Create a new geo-targeted smart link with an optional custom slug.

    Creates a smart link that redirects visitors to the destination URL.
    Optionally configure country-specific geo rules and deep linking for
    iOS/Android apps. Does NOT modify any existing links.

    Returns the created smart link details including its short URL
    (youfil.to/<slug>).

    Common errors:
    - Slug already taken: choose a different slug or omit for auto-generation.
    - Plan limit reached: upgrade your plan to create more links.
    - Invalid URL: ensure the destination URL is a valid HTTP/HTTPS URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false), the description discloses that it returns the created link details including the short URL, and lists common errors (slug taken, plan limit, invalid URL). This is useful behavioral context for a create operation.

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 and front-loaded: a concise one-sentence purpose followed by a clear return-value note and a bulleted list of common errors. Every sentence adds value with no redundancy.

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 create operation with optional geo-targeting and deep-link config, the description covers creation, return value, non-modification, and error scenarios. It is complete enough 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.

Parameters3/5

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

The description highlights geo rules, custom slug, and deep linking, but the schema already provides thorough descriptions for all parameters. It doesn't mention redirect_type or response_format, though these are documented in the schema, so the description adds some context but not full compensation.

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 it creates a new geo-targeted smart link with an optional custom slug. The verb 'Create' and resource 'smart link' are specific, and the phrase 'Does NOT modify any existing links' distinguishes it from update/delete tools.

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 implicitly says when to use (to create a smart link) and provides a clear exclusion ('Does NOT modify any existing links'), which steers toward update for modifications. Common errors give practical guidance, though it doesn't explicitly name alternative tools.

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