Skip to main content
Glama

Youfiliate Smart Links

by io.github.andrewmpierce
OverviewDiscussionsAdmin

youfiliate_disconnect_youtube

DestructiveIdempotent

Disconnect your YouTube account from Youfiliate.

    IMPORTANT: Always confirm with the user before executing this action.
    The `confirm` parameter must be set to true. This removes stored OAuth
    tokens. You will need to reconnect to use the auto-migration feature.

    Does NOT modify any YouTube data or video descriptions.

    Common errors:
    - Not connected: no YouTube account to disconnect.
    - confirm=False: you must set confirm=True after getting user confirmation.

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.8/5.0
Behavior5/5

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

Beyond annotations (destructive, idempotent), the description adds crucial context: it removes stored OAuth tokens, does NOT modify YouTube data, and explains common errors such as 'not connected' and 'confirm=False'. This gives the agent a thorough understanding of consequences and edge cases.

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 with the main action first, followed by important warnings, effects/non-effects, and common errors in bullet form. Every line serves a purpose and the layout 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?

For a destructive disconnect operation, the description covers prerequisites (user confirmation), effects (token removal), non-effects (no YouTube data modification), and failure cases. Since an output schema exists, return value details are unnecessary. The description is fully complete for the tool's complexity.

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

Parameters5/5

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

The only parameter, confirm, is thoroughly explained: must be set to true, requires user confirmation, and the error case confirm=False is called out. This fully covers parameter semantics despite the schema coverage signal of 0%, because the description explicitly handles the parameter's meaning and required value.

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 'Disconnect your YouTube account from Youfiliate' with a specific verb and resource, distinguishing it from sibling tools like connect_youtube. The purpose is unambiguous and directly reflects the tool's function.

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 explicit usage guidance: always confirm with the user, set confirm to true, and notes the need to reconnect for auto-migration. It clearly implies when to use the tool, though it does not explicitly name alternative tools beyond this context.

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