Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Download Media Captions

download_media_captions
Idempotent

Downloads a lecture’s caption track and saves it as a text transcript on local disk for offline review or note-taking.

Instructions

Download a lecture's caption track and save it as a text transcript on local disk. Returns the saved path. Get media_id from list_media_objects and track_id from get_media_captions.

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": {
      "media_id": "<media_id>"
    },
    "name": "download_media_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_dirNoFolder to save into: the server's download folder (CANVAS_DOWNLOAD_DIR) or a folder inside it, such as "week1". Anywhere else is refused. Leave it out to use the download folder itself.
media_idYesMedia object ID, e.g. "m-abc123". Get it from list_media_objects.
track_idNoDefaults to the first English track

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / dest_dir / description
      Previous value: -"Local folder to save into. Defaults to the server's download folder (CANVAS_DOWNLOAD_DIR)."New value: +"Folder to save into: the server's download folder (CANVAS_DOWNLOAD_DIR) or a folder inside it, such as \"week1\". Anywhere else is refused. Leave it out to use the download folder itself."
  2. Changed2 schema fields changedv1.1.3
    • addedInput schema / properties / dest_dir / description
      Added value: +"Local folder to save into. Defaults to the server's download folder (CANVAS_DOWNLOAD_DIR)."
    • addedInput schema / properties / media_id / description
      Added value: +"Media object ID, e.g. \"m-abc123\". Get it from list_media_objects."
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds genuinely new context: the tool writes a file to local disk and returns the saved path, which is the key side effect an agent needs to know.

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?

Three short sentences, front-loaded with the action and outcome, then the return value, then the prerequisite lookups. No wasted wording.

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?

With no output schema, the description correctly states the return value (saved path) and the disk-write behavior. It could mention transcript format or failure behavior for a missing track, but nothing essential for invocation is missing.

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 100% and the schema already documents dest_dir restrictions, the media_id example, and the track_id default. The description's ID-provenance hints largely duplicate the schema, so it adds little beyond the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Download a lecture's caption track and save it as a text transcript on local disk') and clearly distinguishes it from the sibling get_media_captions, which only lists tracks. An agent can tell exactly what this produces.

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?

Explicitly tells the agent where to obtain the required IDs (media_id from list_media_objects, track_id from get_media_captions), which implies the correct call sequence. It stops short of stating when not to use it or what happens if the track is missing.

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

Deploy Server

Other Tools