Skip to main content
Glama
azickri

Repliz MCP Server

by azickri

Delete Content Comment

repliz_delete_content_comment

Remove a specific comment from content using content ID, comment ID, and account ID. This deletion is permanent and cannot be undone.

Instructions

Delete a comment on a piece of content. Irreversible — confirm before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe account id that owns the content.
commentIdYesThe comment id to delete.
contentIdYesThe content id.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly states that deletion is irreversible, a critical behavioral trait. The description does not cover other traits like permissions or side effects, but the destructive nature is sufficiently disclosed.

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 extremely concise with two short sentences. It is front-loaded with the core action and includes the critical irreversibility warning. No extraneous information.

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 simple delete tool with no output schema, the description effectively communicates the essential information: what it does and a key risk (irreversibility). It could mention prerequisites like ownership, but the tool is straightforward enough.

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 input schema has 100% coverage with descriptions for all three parameters. The tool description does not add additional meaning beyond the schema, so a baseline of 3 is appropriate.

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 the action 'Delete' and the resource 'a comment on a piece of content'. The verb and resource are specific, and there is no ambiguity with sibling tools like create, get, or update comment.

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 includes an explicit warning about irreversibility ('Irreversible — confirm before calling.'), guiding agents to exercise caution. It does not explicitly mention when not to use this tool or list alternatives, but the context is clear for a deletion action.

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/azickri/repliz-mcp'

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