Skip to main content
Glama

Read a link posted in a course

bb_read_link
Read-only

Read professor-posted Blackboard course or announcement links, including Google Docs/Slides/Sheets, Drive files, PDFs, web pages, and YouTube metadata; output is paginated and requires a course link.

Instructions

Read a professor-posted course or announcement link. Supports Google Docs/Slides/Sheets exports, Drive files, Colab notebooks, web pages, PDFs, video captions when exposed and YouTube metadata. Requires a link present in the specified Blackboard course. Protected sites may need CLI connect. Text is paginated; limitations are explicit.

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>",
      "url": "<url>"
    },
    "name": "bb_read_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
offsetNo
courseIdYes
pageSizeNo
contentIdNo
announcementIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, it discloses format-dependent behavior, captions only when exposed, possible CLI authentication, and paginated text. Those are meaningful operational details, though the phrase “limitations are explicit” does not explain what limitations or failure behavior to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loads its purpose, and uses each sentence for capabilities, prerequisites, or operational caveats. The long format inventory is somewhat dense and the final “limitations are explicit” clause is less informative than the rest.

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?

It supplies enough context to understand the tool’s general role and operational behavior, but not enough for fully reliable invocation given six undocumented parameters and no output schema. The relationships among courseId, url, contentId, and announcementId, plus pagination and result behavior, remain the main gaps.

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?

With 0% schema description coverage, the description only indirectly explains url and courseId through the course-link requirement and offset and pageSize through “Text is paginated.” It gives no invocation semantics for contentId or announcementId, nor pagination units, defaults, or how the optional identifiers combine with the required URL.

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 opening sentence gives a specific verb and resource—reading a professor-posted course or announcement link—and the format list clarifies the external content being retrieved. It does not explicitly distinguish the tool from siblings such as bb_get_content or bb_get_attachment, so it stops short of top-tier routing clarity.

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?

It gives a concrete precondition that the link must be present in the specified Blackboard course, supported-source context, and an authentication contingency for protected sites. It never says when another course-content or attachment tool is preferable, so the guidance is contextual rather than comparative.

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