Skip to main content
Glama
andrewmpierce

youfiliate-mcp

youfiliate_delete_smart_link

DestructiveIdempotent

Permanently delete a smart link to stop its short URL from working. Confirm with user before executing.

Instructions

Delete a smart link permanently. The short URL will stop working.

IMPORTANT: Always confirm with the user before executing this action. The confirm parameter must be set to true. This is a destructive action that cannot be undone — the slug becomes available for reuse after a cooldown period.

Does NOT affect other links or YouTube descriptions.

Common errors:

  • Smart link not found: check the ID.

  • confirm=False: you must set confirm=True after getting user confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructive and non-read-only. Description adds context: permanent deletion, slug cooldown, no side effects on other resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structured with sections, front-loaded with core action. Some redundancy in repeating confirm parameter details, but overall efficient.

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?

Covers all essential context: destructive nature, user confirmation requirement, common errors, and what is not affected. With output schema present, it is complete for safe invocation.

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 has good descriptions for id and confirm. The tool description reinforces the confirm requirement and adds context about slug cooldown, but schema coverage is actually high (not 0% as indicated).

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 states 'Delete a smart link permanently' with specific verb and resource, and distinguishes from siblings like create or update.

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?

Explicitly warns to confirm with user before executing, and notes that other links and YouTube descriptions are unaffected. Could mention alternatives but sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewmpierce/youfiliate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server