Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce

youfiliate_preview_migration

Read-onlyIdempotent

Preview a YouTube description migration without making changes.

    Performs a dry-run analysis showing how many videos and links would be
    affected. Does NOT modify any data or YouTube descriptions. Requires
    a connected YouTube account.

    Common errors:
    - YouTube not connected: connect first with `youfiliate_connect_youtube`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'Does NOT modify any data or YouTube descriptions' and 'dry-run.' It adds an important prerequisite—requires a connected YouTube account—and a common error note, providing useful context beyond the annotations.

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 compact and front-loaded, with the purpose in the first sentence. Each subsequent sentence adds a distinct fact: dry-run behavior, no data modification, account prerequisite, and a common error. There is minor redundancy between 'without making changes' and 'Does NOT modify,' but it remains appropriately sized.

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 preview/dry-run tool with annotations and an output schema, the description covers the core behavior, safety, prerequisite, and an error case. It gives enough context for an agent to select and invoke it appropriately, and the sibling tool names provide additional context for related operations.

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 tool description provides no parameter-level guidance; it does not mention auto_geo_rules, conversion_mode, or response_format. Although the input schema includes descriptions for these fields, the context signal indicates 0% schema description coverage, and the description fails to compensate by explaining how these options affect the preview.

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 a specific verb and resource: 'Preview a YouTube description migration,' and immediately clarifies it is a dry-run analysis showing affected videos and links. This clearly distinguishes it from siblings like youfiliate_start_migration 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 Guidelines4/5

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

The description states that it performs a dry-run without making changes and requires a connected YouTube account, with a common-error note directing users to youfiliate_connect_youtube. It does not explicitly name youfiliate_start_migration as the alternative for actually executing a migration, so it stops short of full explicit when-not guidance.

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