Skip to main content
Glama

create_page

Add a new page to a Canvas course with custom HTML content. Control visibility, front page setting, and editing permissions.

Instructions

Create a new page in a Canvas course.

    Args:
        course_identifier: Course code or Canvas ID
        title: Page title
        body: HTML content for the page
        published: Whether to publish (default: True)
        front_page: Whether to set as front page (default: False)
        editing_roles: Who can edit (default: "teachers")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
titleYes
bodyYes
publishedNo
front_pageNo
editing_rolesNoteachers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as authorization needs, rate limits, or side effects (e.g., overwriting existing pages, failure scenarios). It only states defaults, not behaviors beyond that.

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 concise and front-loaded with the purpose statement. The Args block is structured but could be slightly more compact. Every sentence adds value, with no redundant filler.

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?

Given the 6 parameters and lack of annotations, the description covers creation semantics adequately but omits usage guidelines and behavioral transparency. The presence of an output schema reduces the need to explain return values, but completeness is moderate.

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?

The input schema has 0% description coverage, but the description's Args section provides clear meaning for each parameter, including types, defaults, and purpose (e.g., 'published: Whether to publish (default: True)'), significantly compensating for the schema gap.

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?

The description explicitly states 'Create a new page in a Canvas course' using a specific verb and resource, clearly distinguishing it from sibling tools like update_page_settings, edit_page_content, and delete_page.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., edit_page_content for modifying existing pages, bulk_update_pages for batch operations). The description implies usage for creation but does not specify exclusions or contexts.

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/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server