Canvas MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Rubric

create_rubric

Destructive

Creates a new rubric in a Canvas course, optionally linking it to an assignment. Define criteria and ratings via JSON to structure grading.

Instructions

Create a new rubric in a course, optionally associating it with an assignment.

Encodes indexed criteria and ratings using bracket-notation form data.

The criteria parameter is a JSON string mapping arbitrary criterion keys to objects with the following fields:

description (required): Short criterion label shown in the rubric grid
points (required): Maximum points for this criterion (non-negative number)
long_description (optional): Detailed criterion description
ratings (optional): List (or object) of rating levels, each with:
- description (required): Rating label (e.g. "Excellent")
- points (required): Points for this rating (non-negative number)
- long_description (optional): Detailed rating description

Example criteria JSON::

{
  "c1": {
    "description": "Content Quality",
    "points": 10,
    "ratings": [
      {"description": "Excellent", "points": 10},
      {"description": "Satisfactory", "points": 7},
      {"description": "Needs Work", "points": 3}
    ]
  },
  "c2": {
    "description": "Grammar",
    "points": 5,
    "ratings": [
      {"description": "No errors", "points": 5},
      {"description": "Minor errors", "points": 3}
    ]
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Rubric title
`criteria`	Yes	JSON string defining rubric criteria (schema and example in the tool description)
`reusable`	No	Make rubric reusable across courses (default: False)
`assignment_id`	No	Optional assignment ID to immediately associate the rubric with
`use_for_grading`	No	When associating with an assignment, use rubric for grade calculation (default: False)
`course_identifier`	Yes	Course code or Canvas ID
`free_form_criterion_comments`	No	Allow free-form comments per criterion instead of rating selection (default: False)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.15.0Oct 24, 2026

changedInput schema / properties / criteria / description

Previous value: -"JSON string defining rubric criteria (see docstring above)"New value: +"JSON string defining rubric criteria (schema and example in the tool description)"

Changed1 schema field changedv1.10.0Aug 20, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null

Changed19 schema fields changedv1.8.0Aug 10, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / assignment_id / description
```
Added value: +"Optional assignment ID to immediately associate the rubric with"
```
- removedInput schema / properties / assignment_id / title
```
Removed value: -"Assignment Id"
```
- addedInput schema / properties / course_identifier / description
```
Added value: +"Course code or Canvas ID"
```
- removedInput schema / properties / course_identifier / title
```
Removed value: -"Course Identifier"
```
- addedInput schema / properties / criteria / description
```
Added value: +"JSON string defining rubric criteria (see docstring above)"
```
- removedInput schema / properties / criteria / title
```
Removed value: -"Criteria"
```
- addedInput schema / properties / free_form_criterion_comments / description
```
Added value: +"Allow free-form comments per criterion\n                          instead of rating selection (default: False)"
```
- removedInput schema / properties / free_form_criterion_comments / title
```
Removed value: -"Free Form Criterion Comments"
```
- addedInput schema / properties / reusable / description
```
Added value: +"Make rubric reusable across courses (default: False)"
```
- removedInput schema / properties / reusable / title
```
Removed value: -"Reusable"
```
- addedInput schema / properties / title / description
```
Added value: +"Rubric title"
```
- removedInput schema / properties / title / title
```
Removed value: -"Title"
```
- addedInput schema / properties / use_for_grading / description
```
Added value: +"When associating with an assignment, use rubric for grade\n             calculation (default: False)"
```
- removedInput schema / properties / use_for_grading / title
```
Removed value: -"Use For Grading"
```
- removedInput schema / title
```
Removed value: -"create_rubricArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"create_rubricOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed8 schema fields changedv1.3.0May 2, 2026

addedInput schema / properties / assignment_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Assignment Id"
+}

removedInput schema / properties / association_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Association Id"
-}

removedInput schema / properties / association_type

Removed value: -{
-  "default": "Assignment",
-  "title": "Association Type",
-  "type": "string"
-}

removedInput schema / properties / criteria / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "type": "object"
-  }
-]

addedInput schema / properties / criteria / type
```
Added value: +"string"
```
changedInput schema / properties / free_form_criterion_comments / default
```
Previous value: -trueNew value: +false
```

removedInput schema / properties / purpose

Removed value: -{
-  "default": "grading",
-  "title": "Purpose",
-  "type": "string"
-}

addedInput schema / properties / reusable

Added value: +{
+  "default": false,
+  "title": "Reusable",
+  "type": "boolean"
+}

Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / title
```
Added value: +"create_rubricArguments"
```
First observedSep 27, 2025

TDQS

B3.1/5.0

Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description does not explain the destructive or non-idempotent consequences, required permissions, or whether creation can be undone. It adds detail about criteria encoding but little behavioral context beyond what the annotations already state.

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?

The description is front-loaded with the core action and then explains the complex criteria format. The example is justified by the complexity of the criteria JSON, though the overall text is somewhat long.

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?

The description adequately covers the most complex input, criteria, but omits return values, permission requirements, and guidance on sibling tools. Given the lack of an output schema and the presence of multiple rubric-related siblings, these gaps keep completeness at a minimum-viable level.

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 already 100%, so the schema documents all seven parameters. The description still adds substantial value for the complex criteria parameter by defining its required and optional fields and providing a complete JSON example.

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?

The description states a specific verb and resource: create a new rubric in a course, with optional assignment association. The scope is clear, but it does not distinguish this tool from siblings such as create_rubric_from_csv or associate_rubric.

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?

Usage is only implied by 'Create a new rubric.' The description gives no guidance on when to use this instead of create_rubric_from_csv, update_rubric, or associate_rubric, nor when to pass assignment_id versus using the separate association tool.

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

Deploy Server

Create Rubric

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools