Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce
OverviewDiscussionsAdmin

youfiliate_connect_youtube

Initiate YouTube OAuth connection. Returns a URL the user must open in their browser.

    The user must open the returned URL in their web browser to authorize
    Youfiliate to access their YouTube channel. The OAuth callback is handled
    in the browser — this tool only returns the authorization URL.

    Does NOT read or modify any YouTube data. The OAuth flow is completed
    in the user's browser.

    Common errors:
    - Already connected: disconnect first with `youfiliate_disconnect_youtube`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses that the tool does NOT read or modify YouTube data, that the OAuth flow completes in the browser, and that only the authorization URL is returned. This adds significant behavioral context beyond the annotations, clarifying the side-effect profile and the division of responsibility between tool and user.

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 with a brief opening sentence, a clear explanation of user action, a note about non-effects, and a bulleted common error. Every sentence serves a purpose, and it is front-loaded with the main purpose.

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?

Given the tool's simplicity, the presence of an output schema, and annotations, the description covers the operational flow, user responsibilities, side-effect clarity, and a likely error case. It is complete for an agent to understand 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 does not discuss the response_format parameter, but the input schema already provides a description and default for it. With schema coverage of the single parameter, the description adds no additional semantic value, so the baseline of 3 applies.

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 'Initiate YouTube OAuth connection' and explains it returns a URL to open in the browser. This clearly identifies the tool's specific action and resource, distinguishing it from siblings like disconnect or status check.

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 explains the user must open the returned URL, and the common error section states that if already connected, one should disconnect first using youfiliate_disconnect_youtube. This provides a clear 'when not to use' and an alternative, though it doesn't explicitly mention checking connection status beforehand.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources