Skip to main content
Glama

Delete content item

bb_delete_content
Destructive

Deletes a Blackboard course content item after write access and confirmation, limited to instructor or designer roles.

Instructions

Delete a content item. Requires BB_ALLOW_WRITES=1, confirm:true and an instructor/designer role.

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>",
      "contentId": "<contentId>"
    },
    "name": "bb_delete_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
courseIdYes
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is structured. The description adds valuable non-annotation context: a required environment flag (BB_ALLOW_WRITES=1), a mandatory confirm:true, and a role gate (instructor/designer). It stops short of saying whether deletion cascades to child items or is recoverable, which would be the next useful disclosure.

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 with zero filler. The action is front-loaded and the preconditions follow immediately, so an agent scanning it gets purpose then gates in order.

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, non-idempotent mutation with no output schema and undocumented parameters, the description covers the authorization gates well but omits consequences: what happens to nested content, whether the operation can be undone, and the error behavior when the item does not exist. Adequate but leaves real gaps for a destructive tool.

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 0% across three parameters, so the description carries the burden. It does explain the non-obvious one — confirm must be true — but says nothing about courseId/contentId formats or whether confirm defaults to false. Partial compensation for a low-coverage 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?

States a specific verb and resource: 'Delete a content item.' An agent can immediately tell this removes an item, and the 'bb_delete_content' name aligns with the description. It does not differentiate itself from siblings like bb_delete_announcement or bb_set_content_visibility, but the resource noun 'content item' does the disambiguating work implicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when it applies (you have a content item to remove) and lists prerequisites — BB_ALLOW_WRITES=1, confirm:true, instructor/designer role — which is real usage context. However, it never says when NOT to use it or names an alternative (e.g., hiding via bb_set_content_visibility instead of deleting), leaving the agent to infer the boundary.

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