Skip to main content
Glama

create_course

Destructive

Create a new course in a Canvas account. Provide account ID and name; optionally set course code and dates. Returns the created course.

Instructions

Create a new course in a Canvas account. Returns the created course object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesThe Canvas account ID to create the course in
nameYesThe name of the course
course_codeNoThe course code (e.g. CS101)
start_atNoCourse start date in ISO 8601 format (e.g. 2026-01-15T00:00:00Z)
end_atNoCourse end date in ISO 8601 format (e.g. 2026-05-15T00:00:00Z)
Behavior4/5

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

Annotations already set destructiveHint=true, and the description confirms destructive behavior. It adds that the tool returns the created course object, which is not in annotations. No contradictions.

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, no fluff. Every word contributes to clarity.

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?

With 5 parameters and no output schema, the description is minimal but adequate. It mentions the return value but lacks details on what the returned object contains. Given schema coverage, it's functional but incomplete.

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%, so each parameter already has a description. The tool description does not add extra meaning beyond the schema.

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?

The description clearly states it creates a new course and returns the created object. It uses a specific verb ('Create') and resource ('course'), distinguishing it from sibling tools that create other entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like create_assignment or update_course. No prerequisites or context are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruchris/canvas-lms-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server