Skip to main content
Glama

Update content item

bb_update_content
Idempotent

Update a Blackboard content item's title, body, or visibility as an instructor or designer, with write access enabled and confirmation required.

Instructions

Update a content item title, body or visibility. 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_update_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
titleNo
confirmNo
visibleNo
courseIdYes
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare a non-read-only, idempotent, non-destructive mutation, and the description adds material context beyond that: a write-gate environment flag, a required confirm flag, and an authorization role. It stops short of describing partial-update semantics (what happens to fields not supplied) or error behaviour on a failed gate.

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 and its fields come first, the hard preconditions second. Every clause carries information an agent needs before invoking.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation with annotations but no output schema, the definition covers the highest-risk items — write gating, confirmation and role requirement — plus the editable fields. The remaining gap is the identity parameters and partial-update behaviour, which are minor for a straightforward update 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%, so the description carries the burden; it names title, body and visibility and explains the confirm gate requirement. It leaves courseId and contentId — the two required identifiers — completely uncharacterized, so half the parameter surface is still opaque.

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 gives a specific verb and resource ('Update a content item') and enumerates the mutable fields (title, body, visibility), so the agent knows exactly what changes. It does not explicitly name the neighbouring visibility-only or delete siblings, so differentiation is left to inference.

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?

It states the preconditions for calling (BB_ALLOW_WRITES=1, confirm:true, instructor/designer role), which is real usage guidance. However, it never says when to prefer a sibling such as bb_set_content_visibility for a visibility-only change, nor any when-not-to-use case.

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