Skip to main content
Glama

Delete own discussion post

bb_delete_discussion_post
Destructive

Delete a discussion post you authored when the forum permits deletion. Provide course, forum, and message IDs with confirm:true to remove the post.

Instructions

Delete a post you authored, where the forum allows deletion. Requires BB_ALLOW_WRITES=1 and confirm:true.

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": {
      "courseId": "<courseId>",
      "forumId": "<forumId>",
      "messageId": "<messageId>"
    },
    "name": "bb_delete_discussion_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdNo
confirmNo
forumIdYes
courseIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations lack: the BB_ALLOW_WRITES=1 environment gate and the confirm:true guard. It does not say whether deletion is recoverable or what happens on failure.

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?

Two short sentences, zero padding, with the scope restriction front-loaded ahead of the operational prerequisites. Every clause earns its place.

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 destructive mutation with no output schema, the write gating and confirm requirement are covered well. But with 0% schema description coverage on three required identifiers, an agent still lacks guidance on how to address the post correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across five parameters, so the description carries the full burden and fails to: only 'confirm:true' is mentioned. courseId, forumId, messageId, and boardId are left entirely undefined, including which are required and whether boardId is optional or an alternative scope.

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?

States a specific verb and resource ('Delete a post') and narrows scope with 'you authored, where the forum allows deletion.' That distinguishes it from broader delete siblings such as bb_delete_content or bb_delete_announcement, though no sibling is named explicitly.

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?

Gives real preconditions: the post must be your own, the forum must permit deletion, BB_ALLOW_WRITES=1 must be set, and confirm must be true. It stops short of naming an alternative tool for cases where these conditions fail (e.g., editing instead of deleting).

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