Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_rollback_migration

Destructive

Roll back a completed migration, restoring original YouTube descriptions.

    IMPORTANT: This modifies YouTube video descriptions. Always confirm with
    the user before executing. This reverts all video descriptions to their
    pre-migration state.

    The rollback runs asynchronously. Requires a connected YouTube account.

    Common errors:
    - Migration not found or not in a rollback-eligible state.
    - YouTube not connected: reconnect first.
    - confirm=False: must set confirm=True after user confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (e.g., destructiveHint=true), the description discloses that execution is asynchronous, it reverts all video descriptions, requires a connected YouTube account, and describes specific failure modes. This is rich behavioral context that helps the agent anticipate side effects and errors.

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-organized: a clear one-sentence summary, an important warning, a note on async behavior and prerequisites, and a succinct bulleted list of common errors. Every sentence adds value, and the structure improves scannability.

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?

The description covers prerequisites (connected account), execution model (async), required user confirmation, irreversible effect, and common error conditions. The tool has an output schema, so return values are presumably documented. This is complete for a rollback operation.

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

Parameters4/5

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

The input schema already provides detailed descriptions for both 'id' and 'confirm', including the confirmation warning. The description adds value by reiterating the confirm=False error and reinforcing the confirmation requirement, but largely relies on the schema. Since schema coverage is effectively high, the slight additional clarification earns a 4.

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 tool's purpose with a specific verb ('Roll back'), the target resource ('a completed migration'), and the effect ('restoring original YouTube descriptions'). This unambiguously distinguishes it from sibling tools like start_migration or preview_migration and any other operation.

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 context: confirm with user, requires connected YouTube account, and lists common errors including rollback-ineligible states and the need to set confirm=True. It does not explicitly name alternative tools, but the guidance is sufficient for an agent to know when to use this tool and what prerequisites must be met.

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