Skip to main content
Glama

remove_post

Delete a specific post from a BAND group using the post identifier and band identifier to manage content and maintain group organization.

Instructions

Delete a post from BAND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
band_keyYesband identifier
post_keyYespost identifier to delete

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
result_codeYesResult code
result_dataYesResult data

Implementation Reference

  • The handler function that executes the remove_post tool by calling the BAND API to delete the post and returning the response.
    export async function handleToolCall(band_key: string, post_key: string) {
      try {
        const params: Record<string, unknown> = { band_key, post_key };
        const deleteData = await bandApiClient.post<RemovePostResponse>(
          "/v2/band/post/remove",
          params
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(deleteData, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(
          `Failed to delete post: ${
            error instanceof Error ? error.message : "Unknown error"
          }`
        );
      }
    }
  • The ToolDefinition object defining the name, description, inputSchema, and outputSchema for the remove_post tool.
    export const ToolDefinition: Tool = {
      name: "remove_post",
      description: "Delete a post 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 to delete",
          },
        },
        required: ["band_key", "post_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:79-83 (registration)
    Registration in the main tool dispatcher switch statement that routes 'remove_post' calls to the handler.
    case "remove_post":
      return removePost.handleToolCall(
        a.band_key as string,
        a.post_key as string
      );
  • src/tools.ts:15-28 (registration)
    Registration of the tool definition in the bandTools array exported for MCP tool listing.
    export const bandTools: Tool[] = [
      profile.ToolDefinition,
      bands.ToolDefinition,
      posts.ToolDefinition,
      post.ToolDefinition,
      comments.ToolDefinition,
      permissions.ToolDefinition,
      albums.ToolDefinition,
      photos.ToolDefinition,
      writeComment.ToolDefinition,
      writePost.ToolDefinition,
      removePost.ToolDefinition,
      removeComment.ToolDefinition,
    ];
  • Index file that bundles and exports the ToolDefinition and handleToolCall for the remove_post tool.
    const removePost = {ToolDefinition, handleToolCall}
    
    export default removePost;
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 basic action. It doesn't disclose whether deletion is permanent/reversible, what permissions are required, if there are rate limits, or what happens to associated data (e.g., comments). The description is minimal and lacks behavioral context.

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. It's front-loaded with the core action and resource, making it immediately understandable 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 this is a destructive operation with no annotations but with an output schema (which handles return values), the description is minimally adequate. However, for a deletion tool, it should ideally include more about permissions, consequences, or error cases to be fully complete.

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 parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying they identify the target post. Baseline 3 is appropriate since the 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 resource ('a post from BAND'), making the purpose immediately understandable. It distinguishes from siblings like 'remove_comment' by specifying the resource type, though it doesn't explicitly contrast with other deletion tools.

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. While it's clear this deletes posts, there's no mention of prerequisites, permissions needed, or when to choose this over similar tools like 'remove_comment' for comment deletion.

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