Skip to main content
Glama

Create page

bb_create_page

Creates an HTML content page inside a Blackboard course module or folder for instructors and designers, with write access enabled and confirmation required.

Instructions

Create a content page with HTML body inside a module/folder. 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>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "bb_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHTML body
titleYes
confirmNo
courseIdYes
parentIdNo

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?

Annotations already establish a non-readonly, non-idempotent, non-destructive write. The description adds meaningful behavior beyond that: an environment flag gate, an explicit confirm:true requirement, and a role restriction, which together signal this is a guarded mutation. It does not describe failure modes or what the created page returns.

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 tight sentences with the action and placement front-loaded and prerequisites trailing. Nothing is redundant or wasted.

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 5-parameter, no-output-schema mutation tool, the definition covers the essential gates (writes flag, confirm, role) and the placement semantics. What remains thin is course/title parameter meaning, but the critical invocation conditions are all present.

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 coverage is only 20% (only 'body' is documented), so the description must compensate. It clarifies that 'body' is HTML and implies 'parentId' is the module/folder target, and gives real meaning to 'confirm' as a safety gate, but 'courseId' and 'title' are left completely unexplained.

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 uses a specific verb and resource ('Create a content page') and adds placement scope ('inside a module/folder'), which distinguishes it from sibling create tools like bb_create_announcement or bb_create_module. It stops short of explicitly naming an alternative, so it falls just under the top band.

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 gives concrete preconditions for invoking the tool (BB_ALLOW_WRITES=1, confirm:true, instructor/designer role), which is useful usage context. However, it never states when to choose this over other content-creation siblings or when not to use it.

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