Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_start_migration

Destructive

Start a YouTube description migration to convert links to smart links.

    IMPORTANT: This modifies YouTube video descriptions. Always confirm with
    the user before executing. Describe the scope (number of videos/links
    affected from the preview) and ask for explicit confirmation.

    The migration runs asynchronously. Use `youfiliate_get_migration_status`
    to track progress.

    Requires a connected YouTube account.

    Common errors:
    - YouTube not connected: connect first.
    - Migration already in progress: wait for it to complete.
    - confirm=False: must set confirm=True after 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?

The description discloses destructive behavior (modifies YouTube descriptions), asynchronous execution, authentication requirements, and typical failure modes. Annotations already include destructiveHint=true and readOnlyHint=false, but the description adds critical context around user confirmation and error handling, going beyond the structured metadata.

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 appropriately sized, with the main purpose and critical warning in the first lines, followed by async behavior, requirements, and errors in a scannable format. Every sentence serves a purpose, and the bullet-point error list improves readability.

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?

The description covers the essential context: purpose, confirmation workflow, async tracking, authentication, and common errors. It references 'the preview' implying youfiliate_preview_migration, though not naming it explicitly. Since an output schema exists, return value details are not needed, making the description largely complete.

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 parameters auto_geo_rules, conversion_mode, or response_format, and only indirectly touches on confirm through the common error 'confirm=False: must set confirm=True after user confirmation.' With 0% schema description coverage, the description fails to compensate for parameter-level details that the input schema alone provides.

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 explicitly states 'Start a YouTube description migration to convert links to smart links,' using a specific verb and resource. It clearly distinguishes the action from sibling tools like youfiliate_preview_migration, youfiliate_get_migration_status, and youfiliate_rollback_migration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: confirm with the user, describe the scope from the preview, and set confirm=True. It names the prerequisite (connected YouTube account), specifies the tracking tool (youfiliate_get_migration_status), and lists common errors with corrective actions, all of which help an agent decide when and how to invoke this tool.

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