Skip to main content
Glama

list_assignments

Read-only

List all assignments in a Canvas course. Filter by bucket (past, overdue, etc.), search term, or IDs, and choose slim (basic fields) or full (all fields) output.

Instructions

List all assignments in a course. Use fields="slim" when enumerating assignments for selection; switch to "full" once you've identified the target. slim returns id, name, due_at, points_possible, published, and course_id only. "full" (default) includes all Canvas fields plus include extras (submission, all_dates, overrides, score_statistics, etc.). Use bucket to filter by past/upcoming/overdue/etc. Other filters: search_term, assignment_ids, order_by.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesThe Canvas course ID
fieldsNoProjection mode: "slim" returns id/name/due_at/points_possible/published/course_id only; "full" (default) returns all fields
includeNoExtra fields to include on each assignment (Canvas include[] param); ignored when fields="slim"
search_termNoPartial name substring to filter assignments by
bucketNoOnly include assignments in the given bucket
assignment_idsNoRestrict to the given list of assignment IDs
order_byNoField to sort the result by
override_assignment_datesNoApply assignment overrides to due/unlock/lock dates (default Canvas behavior: true)
needs_grading_count_by_sectionNoBreak needs_grading_count down by section
post_to_sisNoFilter to assignments that are/are not posted to SIS
Behavior4/5

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

Annotations already indicate read-only and open-world. Description adds context on the 'slim' vs 'full' field sets and what 'full' includes (Canvas fields + include extras), which is useful beyond annotations.

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?

Concise: two main sentences plus a few phrases. Every sentence adds value, no redundancy. Front-loaded with the core action.

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 10 parameters and no output schema, the description sufficiently covers key parameters and usage patterns. It explains the 'slim' vs 'full' distinction and filter options, making the tool complete enough for an agent.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). The description adds meaning by explaining the purpose of 'fields', 'bucket', and other filters, improving over schema-only documentation.

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 'List all assignments in a course' with a specific verb and resource. It distinguishes from sibling tools like 'get_assignment' (single) and 'list_submissions' (different resource).

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?

Provides explicit guidance: use 'fields=slim' for enumeration and switch to 'full' after identifying the target. Also notes bucket and other filters, but does not explicitly exclude alternatives.

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