Skip to main content
Glama

Show or hide content

bb_set_content_visibility
Idempotent

Set whether a course content item is visible to students, letting instructors and designers show or hide materials in Blackboard.

Instructions

Change content visibility for students. 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>",
      "visible": "<visible>"
    },
    "name": "bb_set_content_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
visibleYes
courseIdYes
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, and the description adds real value on top: a write gate (BB_ALLOW_WRITES=1), a confirmation flag, and a role requirement. It does not explain side effects of hiding (e.g., effect on student access to grades/submissions or notifications), so it is strong but not exhaustive.

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: the action first, then the prerequisites. No filler, no restatement of the title, and every clause carries information an agent needs.

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 simple four-parameter mutation with no output schema, the prerequisites and role requirement cover the most important operational facts. Still missing are the meaning of the visible/courseId/contentId inputs and what actually happens to student access when content is hidden, which matters for a visibility tool.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden and only partially delivers: it clarifies that confirm must be true, but courseId, contentId, and visible are never explained. Note the schema marks confirm as optional while the description states confirm:true is required, leaving ambiguity about the actual contract.

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 names a specific verb and resource ("Change content visibility") and scopes it to students, so an agent knows this toggles visibility rather than editing content. It does not explicitly differentiate from siblings like bb_update_content or bb_delete_content, which could also affect whether content is shown, so it stops short of a 5.

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 preconditions for the call (BB_ALLOW_WRITES=1, confirm:true, instructor/designer role), which is useful context for whether the tool will succeed. However, it gives no guidance on when to choose this over bb_update_content or how it relates to listing/getting content, so usage is only implied.

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