Skip to main content
Glama

remove_comment

Delete a comment from BAND by specifying the band, post, and comment identifiers to manage group discussions.

Instructions

Delete a comment from BAND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
band_keyYesband identifier
comment_keyYescomment identifier to delete
post_keyYespost identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
result_codeYesResult code
result_dataYesResult data

Implementation Reference

  • The handler function that makes the API call to delete the comment using bandApiClient.post to the '/v2/band/post/comment/remove' endpoint.
    export async function handleToolCall(
      band_key: string,
      post_key: string,
      comment_key: string
    ) {
      try {
        const params: Record<string, unknown> = { band_key, post_key, comment_key };
        const deleteData = await bandApiClient.post<RemoveCommentResponse>(
          "/v2/band/post/comment/remove",
          params
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(deleteData, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Failed to delete comment: ${
            error instanceof Error ? error.message : "Unknown error"
          }`
        );
      }
    }
  • ToolDefinition including inputSchema (band_key, post_key, comment_key) and outputSchema for the remove_comment tool.
    export const ToolDefinition: Tool = {
      name: "remove_comment",
      description: "Delete a comment from BAND.",
      inputSchema: {
        type: "object",
        properties: {
          band_key: {
            type: "string",
            title: "Band Key",
            description: "band identifier",
          },
          post_key: {
            type: "string",
            title: "Post Key",
            description: "post identifier",
          },
          comment_key: {
            type: "string",
            title: "Comment Key",
            description: "comment identifier to delete",
          },
        },
        required: ["band_key", "post_key", "comment_key"],
      },
      outputSchema: {
        type: "object",
        properties: {
          result_code: {
            type: "number",
            description: "Result code",
          },
          result_data: {
            type: "object",
            description: "Result data",
            properties: {
              message: {
                type: "string",
                description: "Result message",
              },
            },
          },
        },
        required: ["result_code", "result_data"],
      },
    };
  • src/tools.ts:84-89 (registration)
    Registration in the main tool dispatcher switch statement, delegating to the specific handler.
    case "remove_comment":
      return removeComment.handleToolCall(
        a.band_key as string,
        a.post_key as string,
        a.comment_key as string
      );
  • src/tools.ts:27-27 (registration)
    Inclusion of the tool definition in the exported bandTools array.
    removeComment.ToolDefinition,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('Delete') without disclosing behavioral traits. It doesn't mention permissions needed, whether deletion is permanent/reversible, rate limits, or response behavior, which are critical for a destructive operation.

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, efficient sentence with zero waste, front-loading the core action. It's appropriately sized for a simple tool, making every word count without unnecessary elaboration.

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?

Given the tool's complexity (destructive operation with 3 parameters) and no annotations, the description is minimally adequate but incomplete. It states the purpose but lacks behavioral context, and while an output schema exists, the description doesn't address critical aspects like permissions or irreversible effects.

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 the schema fully documents the three parameters (band_key, comment_key, post_key). The description adds no additional meaning beyond implying deletion requires these identifiers, aligning with the baseline when schema does the heavy lifting.

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 clearly states the action ('Delete') and target resource ('a comment from BAND'), providing specific verb+resource pairing. However, it doesn't differentiate from sibling tools like 'remove_post' or 'write_comment' beyond the obvious resource difference, missing explicit distinction in scope or hierarchy.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing post_key), exclusions, or comparisons to sibling tools like 'remove_post' or 'write_comment', leaving usage unclear beyond the basic 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/kanghouchao/band-mcp-server'

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