Skip to main content
Glama

delete_comment

Apaga um comentário do próprio dono.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID do comentário, vindo de `Comentario.id`.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"ID do comentário, vindo de `Comentario.id`."
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits itself. It implies deletion (a destructive action) but does not state permanence, authentication requirements, ownership verification, or any side effects. The phrase 'from its own owner' hints at a restriction but does not make it explicit.

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 a single, compact sentence with no extraneous words. It conveys the essential action and scope efficiently.

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

Completeness3/5

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

For a simple delete operation with one parameter and no output schema, the description is minimally adequate. However, it lacks behavioral warnings (e.g., irreversibility) and does not explicitly state ownership restrictions, which an agent would need to invoke it correctly in all contexts.

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 schema fully describes the single parameter (id) with a clear origin reference, achieving 100% coverage. The description adds no additional meaning beyond what the schema already provides, so the baseline of 3 applies.

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 'Deletes a comment from its own owner' clearly states the action (deletes) and the resource (a comment), and the qualifier 'from its own owner' adds a meaningful scope. It distinguishes this from posting or listing comments, though it does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus sibling comment tools (e.g., post_comment, list_comments). It does not mention conditions, prerequisites, or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation5/5

Each tool addresses a distinct resource/action: favorites vs. history vs. watch recording are clearly separate, and the NSFW consent/pass tools are unambiguous. Even closely related tools like 'get_channel', 'get_channel_guide', and 'legacy_stream' serve different purposes. No two tools appear to do the same thing.

Naming Consistency4/5

Most tools follow a verb_noun pattern (get_, list_, create_, add_, remove_, etc.) with clear conventions. A few exceptions exist like 'billing', 'geo', 'health', and 'me', which are nouns and break the pattern slightly, but the overall style is predictable and readable.

Tool Count2/5

With 47 tools, the server is far beyond the typical well-scoped range (3-15). While the API covers a broad domain (auth, catalog, chat, comments, billing, NSFW), this many tools would be better split into smaller, focused servers. The count feels bloated and could overwhelm an agent.

Completeness4/5

The tool surface is quite comprehensive for a streaming service: it includes auth, user preferences, favorites, history, catalog search, channel details, comments, chat, NSFW consent/passes, billing, and reporting. Minor gaps exist (e.g., no update/delete for categories/groups, no comment editing), but these are not critical dead ends.

Resources