Skip to main content
Glama

Search Users

search_users
Read-only

Find Canvas users by name, login, or email within a single account, with optional email, last-login, avatar, time-zone, or UUID fields and sort controls.

Instructions

Search for users in a single Canvas account by name, login, or email, returning matching Canvas user objects. Use include to add email, last_login, avatar_url, time_zone, or uuid to each result, and sort/order to control the ordering. This is one account-scoped search — to check whether one student is enrolled anywhere across an educator's own active and concluded courses, use find_student_across_courses instead; to list every user in one course without a search term, use list_course_users; to list an entire account's users unfiltered, use list_account_users. Because results carry no enrollment data, pseudonymized mode cannot tell staff from students and anonymizes every returned user's name and email.

Input Schema

NameRequiredDescriptionDefault
sortNoSort field
orderNoSort order
includeNoExtra fields to include on each user (Canvas include[] param)
account_idYesThe Canvas account ID
search_termYesThe search term (name, login, or email)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.15
    • addedInput schema / properties / account_id / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,18}$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / account_id / type
      Removed value: -"number"
  2. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.18.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld, but the description adds a meaningful caveat: pseudonymized mode anonymizes every returned user because results carry no enrollment data. It does not mention pagination or rate limits, so it earns a 4 rather than a 5.

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?

Four sentences, front-loaded with purpose, then include/sort, then alternatives, then a key caveat. Every sentence earns its place.

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 purpose, alternatives, field inclusion, and a critical anonymization caveat. With no output schema, the return value is lightly described, and pagination/result limits for an open-world search are omitted, leaving a small gap.

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%, so the schema already documents all parameters. The description restates the include enum and sort/order purpose but adds no syntax or format details beyond the schema descriptions, making 3 the correct baseline.

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?

States a specific verb (search), resource (users), scope (single Canvas account), and match fields (name, login, email), and explicitly distinguishes itself from three sibling tools.

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

Usage Guidelines5/5

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

Names the exact alternatives (find_student_across_courses, list_course_users, list_account_users) and the conditions that select them, leaving nothing to inference. Also explains how to use include, sort, and order.

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