Skip to main content
Glama
Sign In
mateai-youtube

mateai-youtube

by mategog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

yt_set_safety_settings

Idempotent

Choose which YouTube and TikTok actions require a confirmation prompt before running, so the user decides what asks for approval. Video deletion always asks and cannot be disabled.

Instructions

DANGEROUS — the server asks the user in a confirmation dialog before this runs. Choose which actions ask the user for a yes before they run. confirm is the full list of optional actions that should ask (an empty list means only the always-on ones ask). Deleting a video always asks and cannot be turned off. Use only with the user's explicit choice, normally via the /yt-safety command.

Input Schema

NameRequiredDescriptionDefault
confirmYesTool names that must ask first, e.g. ['yt_reply_comment', 'yt_post_comment'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • removedInput schema / properties / user_confirmed
      Removed value: -{
-  "description": "Set true ONLY after the user explicitly approved this exact action in chat. Never set it on your own.",
-  "type": "boolean"
-}
  2. Addedv0.7.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses that a server-side confirmation dialog precedes execution, that an empty list falls back to always-on confirmations, and that video deletion is permanently gated. That is real behavioral context an agent cannot infer from readOnlyHint=false / idempotentHint=true / destructiveHint=false.

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 risk warning is front-loaded in the first clause, followed by purpose, parameter semantics, and the deletion exception. Four short sentences with no filler; every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter configuration tool with full schema coverage and no output schema, the description covers purpose, precondition (user's explicit choice), and the key edge cases. It is only slightly thin on what the tool returns or how a failed/partial setting change surfaces.

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?

Schema coverage is 100% and the enum is documented there, so the baseline is 3. The description adds meaning the schema does not: `confirm` is the complete list (replacement semantics, not additive), and an empty list has a specific meaning. It doesn't explain what happens to invalid or unknown tool names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action on a specific resource: it configures which actions must ask the user for confirmation before running. That is unambiguous and distinct from the read-only siblings. It stops short of naming its counterpart yt_get_safety_settings, so sibling routing relies on the tool name alone.

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?

It gives an explicit constraint ('Use only with the user's explicit choice, normally via the /yt-safety command') and an exclusion ('Deleting a video always asks and cannot be turned off'). It does not say when to prefer the getter or what to do if the user hasn't specified a preference, but the context is clear.

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

Deploy Server

Other Tools