esa MCP Server

Official

by esaio

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Delete a comment

esa_delete_comment

Destructive

Deletes a comment from an esa team using its comment ID, enabling removal of outdated or unwanted comments from a team's articles.

Instructions

Deletes a comment from an esa team by comment ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "commentId": "<commentId>"
    },
    "name": "esa_delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`teamName`	No	Team name (required). Use esa_get_teams first to see available teams.
`commentId`	Yes	The comment ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.15.1Oct 31, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv0.13.0Jun 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description merely restates that it deletes a comment and adds no extra behavioral context such as irreversibility, permission requirements, or effects on related data.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, though its brevity contributes to missing context rather than being a model of structured guidance.

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 two-parameter destructive tool with full schema coverage and annotations, the description is minimally adequate. However, it does not mention the teamName parameter or clarify the permanence of deletion, leaving some context to the schema and annotations.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema, including teamName's guidance to use esa_get_teams. The description mentions deletion by comment ID but adds no semantic detail beyond the schema.

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 uses a specific verb and resource: 'Deletes a comment' from an esa team by comment ID. It is clear what the tool does and naturally distinguishes it from sibling comment tools like get/update/create, 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?

There is no guidance on when to use this tool versus alternatives such as update_comment or get_comment, nor any stated prerequisites. The schema mentions using esa_get_teams first for teamName, but the description itself gives no usage context.

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