Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_delete_smart_link

DestructiveIdempotent

Delete a smart link permanently. The short URL will stop working.

    IMPORTANT: Always confirm with the user before executing this action.
    The `confirm` parameter must be set to true. This is a destructive
    action that cannot be undone — the slug becomes available for reuse
    after a cooldown period.

    Does NOT affect other links or YouTube descriptions.

    Common errors:
    - Smart link not found: check the ID.
    - confirm=False: you must set confirm=True after getting user confirmation.

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?

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description goes beyond this by disclosing permanent removal, short URL failure, slug reuse after a cooldown period, and common errors. No contradiction with annotations exists.

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 description is front-loaded with the core purpose and uses structured bullet points for important warnings and common errors. It is efficient, though the confirm requirement is repeated in the IMPORTANT section and the common-errors section.

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 destructive delete tool with an output schema and relevant annotations, the description fully covers effects, irreversibility, confirmation workflow, scope, cooldown behavior, and common errors. It is complete for an agent to decide and execute the operation.

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 documents `id` as a UUID and `confirm` as a required confirmation flag. The description reinforces the confirm workflow and mentions checking the ID in errors, but adds little new meaning beyond the schema. Since schema descriptions are already detailed, the baseline is adequate.

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 opens with 'Delete a smart link permanently. The short URL will stop working,' which clearly specifies the verb, resource, and direct consequence. This distinguishes it from sibling tools like create, update, or get smart links.

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?

Provides explicit workflow guidance: always confirm with the user, set confirm=true, and warns that deletion is irreversible. It also clarifies scope ('Does NOT affect other links or YouTube descriptions') but does not explicitly name alternative tools or when-not conditions compared to siblings.

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