Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

update_page_settings

Update publication status, front page assignment, editing roles, and notification preferences for an existing Canvas page without altering its content.

Instructions

Update settings for an existing page (without changing content).

    Args:
        course_identifier: Course code or Canvas ID
        page_url_or_id: Page URL slug or page ID
        published: True to publish, False to unpublish
        front_page: True to make this the course front page
        editing_roles: One of: teachers, students, members, public
        notify_of_update: True to notify users of the update

    IMPORTANT: The front page cannot be unpublished. First set another page as front page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
page_url_or_idYes
publishedNo
front_pageNo
editing_rolesNo
notify_of_updateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Discloses key constraint that front page cannot be unpublished and notes no content changes, but lacks detail on permissions or side effects; with no annotations, the description carries the burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Concise with clear structure: purpose sentence, parameter list, and an important note. No unnecessary text.

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?

Covers parameters and crucial constraints; output schema exists so return values are not needed. Lacks error handling info but generally sufficient.

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?

Despite 0% schema coverage, description explains each parameter clearly (e.g., allowed values for editing_roles), adding meaning beyond type/required info.

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?

Clearly states it updates settings for an existing page without changing content, distinguishing it from tools like edit_page_content.

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?

Implies when to use (for settings only) but lacks explicit guidance on alternatives or when not to use; the sibling list is large and no direct comparisons.

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