Skip to main content
Glama

get_users

Read-onlyIdempotent

Retrieve a paginated list of all school users, with optional filters by role, status, tags, registration date, and custom fields. Use to manage user data programmatically.

Instructions

🟢 READ-ONLY · Users · GET /v2/users

Get all users

Returns a list with all the users of the school. The users are in sorted order, with the most recently created user appearing first, and the list is paginated, with a default limit of 20 users per page. To refine the list of users, there are a number of query params outlined in the following section; In case more than one Query param is provided, then all of them will be applied (AND operator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoFilter by the page number. In case page number is higher than the maximum one, the results of last page will be returned
roleNoFilter by user role
tagsNoFilter by tags. For several tag values, a comma separated string can be provided.
statusNoFilter by user status
cf_$field_nameNoFilter by custom field. All custom fields start with the cf_ prefix; the "$field_name" part should be replaced by the name of the corresponding custom field. Also, it is possible to use more than one custom fields as filters, using the aforementioned convention.
items_per_pageNoFilter by the items per page number
include_suspendedNoFilter by include_suspended flag. The default value is false.
registration_afterNoFilter by registration after the given datetime (expected in UNIX timestamp format)
registration_beforeNoFilter by registration before the given datetime (expected in UNIX timestamp format)
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds key behaviors: READ-ONLY label, sorting by most recent first, default 20 per page, pagination, AND filtering. No contradiction with annotations.

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?

Front-loaded with emoji, method, and endpoint. Sentences are efficient but slightly redundant ('Get all users' and 'Returns a list'). Could be slightly more concise.

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 read-only list tool with 9 parameters and no output schema, the description covers output format (list, sorted, paginated, limit 20) and filtering logic. Missing details like total count or next page indicators, but adequate.

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?

Schema coverage is 100%, so parameters are well-described individually. The description adds value by explaining that multiple query params combine with AND logic, which is not evident from individual param descriptions.

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 'Get all users' and explains it returns a list of school users with sorting and pagination. It distinguishes from sibling tools like 'get_user' (single) and 'get_users_community_space' (filtered).

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 description explains that query params refine the list with AND logic, but does not explicitly state when to use this tool versus alternatives like 'get_user' or 'get_users_per_course'. No exclusion or when-not guidance.

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/ohneben/Learnworlds-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server