Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Discussion Entries

list_discussion_entries
Read-only

Retrieve discussion posts for a Canvas topic, with optional full text and replies, to review course conversations and group discussions.

Instructions

List discussion entries (posts) for a specific discussion topic with optional full content and replies.

Input Schema

NameRequiredDescriptionDefault
group_idNoCanvas group ID, to read a discussion inside a group space instead of the course (default: None). Discussions that students start in a group exist only there. The group must belong to the course.
topic_idYesDiscussion topic ID
include_repliesNoFetch replies for each entry (default: False)
course_identifierYesCourse code or Canvas ID
include_full_contentNoReturn the complete text of every entry and reply (default: False, which shows short previews)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.15.0
    • addedInput schema / properties / group_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Canvas group ID, to read a discussion inside a group\nspace instead of the course (default: None). Discussions that\nstudents start in a group exist only there. The group must\nbelong to the course."
+}
    • changedInput schema / properties / include_full_content / description
      Previous value: -"Fetch full content for each entry (default: False)"New value: +"Return the complete text of every entry and\nreply (default: False, which shows short previews)"
  2. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  3. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / include_full_content / description
      Added value: +"Fetch full content for each entry (default: False)"
    • removedInput schema / properties / include_full_content / title
      Removed value: -"Include Full Content"
    • addedInput schema / properties / include_replies / description
      Added value: +"Fetch replies for each entry (default: False)"
    • removedInput schema / properties / include_replies / title
      Removed value: -"Include Replies"
    • addedInput schema / properties / topic_id / description
      Added value: +"Discussion topic ID"
    • removedInput schema / properties / topic_id / title
      Removed value: -"Topic Id"
    • removedInput schema / title
      Removed value: -"list_discussion_entriesArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"list_discussion_entriesOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"list_discussion_entriesArguments"
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description does not contradict the readOnlyHint: true annotation. It adds modest context by mentioning the options for 'full content' and 'replies,' which gives the agent a better mental model of the tool's capabilities beyond just the schema definitions.

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?

The definition is highly concise, presented in a single, active sentence that front-loads the core function and resource. There is no redundancy.

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 detailed 100% parameter coverage, the description is minimally complete for an agent. However, it lacks behavioral details about pagination or the typical return format, which would elevate this score.

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

Parameters3/5

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

With 100% schema description coverage, the schema already provides exhaustive semantics for all five parameters (group_id, topic_id, include_replies, course_identifier, and include_full_content). The description adds no value beyond naming the resource.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool clearly states its function: listing discussion entries (posts) within a specific discussion topic. While it doesn't aggressively differentiate from every sibling (like get_discussion_entry_details), it clearly defines the resource (entries) and the context (a specific topic).

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?

The description fails to provide guidance on when to use this tool versus other similar tools (e.g., get_discussion_with_replies). It mentions optional full content and replies but does not state the specific scenario where this list-based tool is preferred over fetching details for specific entries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools