Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

list_submissions_awaiting_grading

Read-only

Lists ungraded student submissions and pending-review quiz essays in a course, grouped by assignment or Classic Quiz, with per-submission details.

Instructions

Lists all submissions in a course that still need a human grade, sorted oldest-waiting first.

Surfaces two categories:

  • workflow_state=submitted: assignments submitted by students but not yet graded at all.

  • workflow_state=pending_review: Classic Quiz submissions where Canvas auto-graded the objective questions but left essays or manually-scored questions for the instructor.

Returns a triage list grouped by assignment or Classic Quiz, with per-submission details: student identity, workflow state, submitted_at, and whether the submission has pending manual-grading questions.

Parameters:

  • course_id (required): Canvas course ID to scan.

  • assignment_ids (optional): limit the scan to specific assignment IDs.

  • include_quizzes (default true): include Classic Quiz assignments in the scan.

  • include_assignments (default true): include non-quiz assignments.

  • only_pending_review (default false): when true, return only pending_review submissions (quiz essays awaiting manual scoring), omitting regular ungraded assignments.

Known limitations:

  • New Quizzes (Quizzes.Next) may not appear with 'pending_review' workflow state here; use SpeedGrader or the New Quizzes interface for their grading queue.

  • Fill-in-the-blank answers that Canvas auto-marked are not surfaced.

  • V1 returns submission-level state only; per-question detail is not included.

  • When CANVAS_PSEUDONYMIZE_STUDENTS is enabled, student names are replaced with pseudonyms. Use resolve_pseudonym to look up the real identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesCanvas course ID to scan for submissions awaiting grading.
assignment_idsNoLimit the scan to these specific assignment IDs (numeric Canvas IDs). When omitted, all assignments in the course are scanned.
include_quizzesNoInclude Classic Quiz assignments in the scan. Default: true. New Quizzes are always covered by the global New Quizzes caveat — see response.caveats.
include_assignmentsNoInclude non-quiz assignments in the scan. Default: true.
only_pending_reviewNoWhen true, return only submissions with workflow_state=pending_review — quiz essays and manually-scored questions that Canvas auto-graded but left for human review. When false (default), return both submitted (ungraded) and pending_review submissions.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Discloses that this is a read-only listing, consistent with annotations. Adds valuable behavioral details: sorting order, pseudonymization when enabled, and known limitations (New Quizzes, fill-in-the-blank, per-question detail). This significantly enhances the annotations.

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?

Well-structured with sections, but somewhat verbose. Could condense some parameter explanations, but overall front-loaded with the main purpose and easy to scan. Earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description thoroughly explains the return format (triage list grouped by assignment, per-submission details). Covers all parameters, limitations, and edge cases like pseudonymization. Very complete for a listing tool.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: explains the distinction between Classic and New Quizzes for include_quizzes, clarifies workflow_state filtering for only_pending_review, and provides default behaviors. This goes well 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?

Clearly states it lists submissions needing human grading, sorted by oldest first. Distinguishes two workflow states (submitted, pending_review) and provides detailed context. The verb 'lists' and resource 'submissions awaiting grading' are specific and unambiguous.

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 describes when to use this tool (to find submissions needing grading) and notes limitations for New Quizzes and fill-in-the-blank. Does not directly compare to sibling tools like list_submissions or grade_submission, but the context is clear enough.

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