list_pagesList pages in a specific Canvas course by course code or ID, with options to sort, filter by published status, and search by term.
List pages for a specific course.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort by 'title', 'created_at', or 'updated_at' | title |
| order | No | 'asc' or 'desc' | asc |
| published | No | Filter by published status (None for all) | |
| search_term | No | Filter pages containing this term | |
| course_identifier | Yes | Course code or Canvas ID |
Changes observed during successful MCP inspections.
v1.10.0Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "type": "string"
- }
- },
- "required": [
- "result"
- ],
- "type": "object",
- "x-fastmcp-wrap-result": true
-}New value: +nullv1.8.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / course_identifier / descriptionAdded value: +"Course code or Canvas ID"Input schema / properties / course_identifier / titleRemoved value: -"Course Identifier"Input schema / properties / order / descriptionAdded value: +"'asc' or 'desc'"Input schema / properties / order / titleRemoved value: -"Order"Input schema / properties / published / descriptionAdded value: +"Filter by published status (None for all)"Input schema / properties / published / titleRemoved value: -"Published"Input schema / properties / search_term / descriptionAdded value: +"Filter pages containing this term"Input schema / properties / search_term / titleRemoved value: -"Search Term"Input schema / properties / sort / descriptionAdded value: +"Sort by 'title', 'created_at', or 'updated_at'"Input schema / properties / sort / titleRemoved value: -"Sort"Input schema / titleRemoved value: -"list_pagesArguments"Output schema / properties / result / titleRemoved value: -"Result"Output schema / titleRemoved value: -"list_pagesOutput"Output schema / x-fastmcp-wrap-resultAdded value: +truev1.0.0Input schema / titleAdded value: +"list_pagesArguments"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already tells the agent this is a safe read, so the description is not obliged to restate safety. Beyond that it adds almost nothing: no mention of pagination, default/max result size, or whether unpublished pages are included unless filtered. For a list tool with no output schema, that leaves meaningful behavioral gaps.
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?
A single front-loaded sentence with zero filler. It is efficient, though the brevity is achieved by omitting information rather than by tight phrasing.
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?
With five parameters, no output schema, and many page-related siblings, the definition should clarify result shape, pagination, and how it differs from fetching a single page. The one-line description leaves those gaps unaddressed.
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?
Schema description coverage is 100%, with sort, order, published, search_term, and course_identifier all documented inline (including accepted values and defaults). The description contributes nothing beyond the schema, so the baseline 3 applies.
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 (list) and resource (pages) plus the scoping requirement (a specific course), so the agent knows what it returns. It does not distinguish itself from close siblings like get_page_details, get_page_content, or get_front_page, leaving the agent to infer that this returns a collection rather than a single page.
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?
No guidance on when to choose this over get_page_details/get_page_content/get_front_page, and no mention of prerequisites such as needing the course identifier. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.