Canvas LMS MCP Server

List Submissions

list_submissions

Read-only

List all submissions for an assignment. Use include to attach user, assignment, rubric_assessment, submission_history, or visibility. Filter with student_ids, workflow_state, or grading_period_id.

Instructions

Input Schema

TableJSON Schema

Name	Required	Description
`grouped`	No	Return one submission per group rather than per student
`include`	No	Extra fields to include (Canvas include[] param). Defaults to ["submission_comments"] when omitted.
`course_id`	Yes	The Canvas course ID
`section_ids`	No	Restrict to submissions in these sections
`student_ids`	No	Restrict to submissions for these user IDs (pass large IDs as strings). Use "all" or "self" for shortcuts.
`assignment_id`	Yes	The Canvas assignment ID
`workflow_state`	No	Only include submissions in this workflow state
`grading_period_id`	No	Restrict to a grading period

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.18.15Oct 14, 2026

addedInput schema / properties / assignment_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / assignment_id / type
```
Removed value: -"number"
```

addedInput schema / properties / course_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / course_id / type
```
Removed value: -"number"
```

addedInput schema / properties / grading_period_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / grading_period_id / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / grading_period_id / minimum
```
Removed value: --9007199254740991
```
removedInput schema / properties / grading_period_id / type
```
Removed value: -"integer"
```

addedInput schema / properties / section_ids / items / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / section_ids / items / type
```
Removed value: -"number"
```

changedInput schema / properties / student_ids / description

Previous value: -"Restrict to submissions for these user IDs. Use \"all\" or \"self\" for shortcuts."New value: +"Restrict to submissions for these user IDs (pass large IDs as strings). Use \"all\" or \"self\" for shortcuts."

addedInput schema / properties / student_ids / items / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  },
+  {
+    "enum": [
+      "all",
+      "self"
+    ],
+    "type": "string"
+  }
+]

removedInput schema / properties / student_ids / items / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

Changed1 schema field changedv1.18.11Sep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv1.18.8Sep 2, 2026
- removedInput schema / properties / student_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]
```
- addedInput schema / properties / student_ids / items / type
```
Added value: +[
+  "number",
+  "string"
+]
```
First observedv1.18.0May 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the default include of submission_comments. It does not mention pagination or result volume, so it adds modest value 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the core action, then include options, then filters. Slightly redundant with the schema on the submission_comments default, but otherwise economical and well ordered.

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?

For an 8-parameter read tool with 100% schema coverage and no output schema, the description covers the main optional behaviors. It omits references to `grouped` and `section_ids`, but those are fully documented in the schema, so nothing critical is missing for correct invocation.

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 description coverage is 100%, so the schema already documents all 8 parameters. The description restates a subset of include values and filter params, adding little beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

States a clear verb+resource: 'List all submissions for an assignment.' An agent can identify the core operation immediately. However, it doesn't differentiate itself from closely related siblings like list_submissions_awaiting_grading or get_my_submissions, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

Provides practical usage detail (which `include` values attach what, and which params filter), which implies how to call it. But there is no explicit when-to-use vs alternatives guidance, e.g. versus list_submissions_awaiting_grading, so routing between sibling tools is left to inference.

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

Deploy Server

List Submissions

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools