Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Group Members

list_group_members
Read-onlyIdempotent

List a Canvas student group's members with names and user IDs using a group ID from list_my_groups; read-only, with optional pagination to view all members.

Instructions

List the members of a student group with names and user IDs. Read-only. Get group_id from list_my_groups.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>"
    },
    "name": "list_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
group_idYesStudent group ID (numeric string). Get it from list_my_groups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of items to return (one page of results). Smaller is faster.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / group_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Student group ID (numeric string). Get it from list_my_groups."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read-only' line is largely redundant. It adds no context on ordering, page-size defaults, membership visibility rules, or what happens with an invalid group_id, leaving useful behavioral detail undisclosed.

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?

Three short sentences, front-loaded with the action and its output shape, followed by the safety note and the parameter-source hint. There is no filler and no sentence that fails to carry information.

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?

For a simple three-parameter list tool with full schema coverage and safety annotations, the description covers what the tool returns and where the required ID comes from. Given no output schema exists, a brief note on result shape or pagination behavior would have closed the remaining gap, but nothing critical to correct invocation is missing.

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?

Schema coverage is 100%, with page, limit, and group_id each documented in-schema, so the baseline is 3. The description only restates the group_id source hint already present in the schema text and adds nothing about pagination semantics beyond 'use it when a result says there are more', which the schema already supplies.

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 description names a specific verb and resource ('List the members of a student group') and even previews the returned fields (names and user IDs), which is more than the tautological title. It stops short of explicitly contrasting with nearby tools like get_group or list_course_users, so it is clear but not fully sibling-differentiated.

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?

The only guidance is a prerequisite pointer: 'Get group_id from list_my_groups.' That tells the agent where the required parameter comes from, but says nothing about when to prefer this tool over list_course_users, get_group, or list_my_groups itself, and gives no exclusions.

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