delete_pageRemove a wiki page from a Canvas course using its URL slug. Permanently deletes the page, making it unavailable to students.
Delete a wiki page from a course. This action is permanent.
| Name | Required | Description | Default |
|---|---|---|---|
| page_url | Yes | The page URL slug to delete | |
| course_id | Yes | The Canvas course ID |
| Name | Required | Description | Default |
|---|---|---|---|
| deleted | Yes | ||
| page_url | Yes |
Changes observed during successful MCP inspections.
v1.18.11Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.18.9Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "deleted": {
+ "const": true,
+ "type": "boolean"
+ },
+ "page_url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "deleted",
+ "page_url"
+ ],
+ "type": "object"
+}v1.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation destructiveHint=true already flags the destructive nature; the description adds a valuable 'permanent' warning that goes beyond the hint. No further behavioral claims are made, but for a simple delete action this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no redundant wording. The action is stated firsthola and the irreversible consequence is highlighted immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation with only two documented parameters in the schema)Skip the context is sufficient. The permanent consequence is stated)Skip and the annotations cover safety profile. It does not discuss prerequisites or edge cases, but none are essential for invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents both required parameters with 100% coverage. The description adds no parameter-level information, so the schema is the primary source; this is an acceptable baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Delete'), a precise object ('wiki page'), and the containment scope ('from a course'). This clearly distinguishes it from deletion tools for other resource types.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it: when you need to delete a wiki page. However, it offers no explicit guidance on alternatives, prerequisites, or situations where this tool should not be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.