Skip to main content
Glama

add_module_item

Add a File, Page, Discussion, Assignment, Quiz, SubHeader, ExternalUrl, or ExternalTool item to a Canvas module using the course code and module ID, with support for completion requirements and positioning.

Instructions

Add an item to a module.

    IMPORTANT: content_id required for File, Discussion, Assignment, Quiz, ExternalTool. page_url required for Page. title required for SubHeader, ExternalUrl.

    Args:
        course_identifier: Course code or Canvas ID
        module_id: Target module ID
        item_type: One of: File, Page, Discussion, Assignment, Quiz, SubHeader, ExternalUrl, ExternalTool
        content_id: Canvas ID of the content (required for File, Discussion, Assignment, Quiz, ExternalTool)
        title: Item title (required for SubHeader, ExternalUrl; optional for others)
        position: Position within module (1-indexed)
        indent: Indentation level (0-4)
        page_url: URL slug of the page (required for Page type)
        external_url: URL for ExternalUrl items
        new_tab: Open external links in new tab (default: False)
        completion_requirement_type: One of: must_view, must_submit, must_contribute, min_score, must_mark_done
        completion_requirement_min_score: Minimum score (only for min_score type)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
module_idYes
item_typeYes
content_idNo
titleNo
positionNo
indentNo
page_urlNo
external_urlNo
new_tabNo
completion_requirement_typeNo
completion_requirement_min_scoreNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not mention side effects (e.g., ordering changes, permission requirements, or idempotency), leaving the agent unaware of behavioral implications beyond the action name.

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 opens with a clear summary and then lists parameters in a readable format. It is somewhat lengthy but well-organized, though the 'IMPORTANT' line and subsequent parameter list overlap slightly.

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?

Given the complexity (12 parameters, no schema descriptions), the description covers all usage requirements comprehensively. The presence of an output schema means missing return value information is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully compensates by detailing each parameter's meaning, conditional requirements, and valid values (e.g., '1-indexed' for position, 'must_view' for completion_requirement_type). This adds significant value over the bare schema.

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 clearly states 'Add an item to a module.' and lists all item types and parameter requirements, making the tool's purpose and scope unambiguous. It distinguishes itself from sibling tools like delete_module_item or list_module_items by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit conditional requirements for different item types (e.g., 'content_id required for File'), which guides proper usage. However, it does not mention when to use alternatives like update_module_item or other tools, leaving some context unaddressed.

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