Skip to main content
Glama

list_course_enrollments

Read-only

Retrieve course enrollments with filters for role, state, user, and grade data.

Instructions

List enrollments within a specific course with Canvas filters. Use include=grades / include=current_points for richer grade data, type[] to limit to a role, and user_id to focus on a single user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesThe Canvas course ID
typeNoFilter by one or more enrollment types
stateNoFilter by enrollment states
roleNoFilter by custom role names
includeNoExtra fields to include (Canvas include[] param)
user_idNoFilter to a specific user (may be numeric ID or "self")
grading_period_idNoScope grade-related includes to this grading period
enrollment_term_idNoLimit to enrollments in the given term
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description is consistent. It adds that the tool uses Canvas filters and hints at grade data, which is helpful. However, it does not mention pagination or limits, a minor gap for a list operation.

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?

The description is a single sentence giving key usage tips, with no wasteful words. It is front-loaded and efficient.

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?

Given 8 parameters fully described in schema and readOnly annotations, the description covers essentials. It lacks mention of return format (e.g., enrollment objects), but overall is adequate for a filterable read operation.

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?

Input schema has 100% description coverage, so parameters are well-defined. The description reinforces some uses (like include=grades) but adds no new semantics beyond the schema, meeting the baseline for full coverage.

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 lists enrollments within a specific course, using the verb 'list' and the resource 'enrollments'. It distinguishes from siblings like 'enroll_user' (create) and 'list_enrollments' (generic) by specifying 'within a specific course'.

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?

The description provides examples of when to use specific parameters (include=grades, type[], user_id), giving clear context. However, it does not explicitly state when not to use this tool versus alternatives like list_course_users, leaving some ambiguity.

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