Skip to main content
Glama
gobeyondidentity

@beyondidentity/mcp

Official
by gobeyondidentity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_users

Read-only

Retrieve a paginated list of all users in a tenant, with filtering by email, username, or other attributes.

Instructions

List all users for the tenant. Returns user objects with pagination (page_size, skip, filter, order_by). Supports filtering by email, username, and other attributes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of items to skip. This is the zero-based index of the first result.
filterNoFilter query for responses. The syntax follows the SCIM grammar from [RFC7644 Section 3.4.2.2](https:datatracker.ietf.org/doc/html/rfc7644#section-3.4.2.2). The supported operations are: - pr (pre
order_byNoA comma-delimited list of attributes to sort results. The default sorting order per attribute is ascending. Therefore, if you want descending order, append the " desc" suffix to the attribute name.
page_sizeNoThe number of items returned per page. The response may include this exact number or fewer. If omitting this value, the response returns the default number of results the method allows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already confirm this is a safe read operation. The description adds pagination context, which is helpful for behavior. However, it does not disclose return limits, default page sizes, or any other operational constraints beyond basic pagination.

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 is a single, efficient sentence that front-loads the core action. It is appropriately sized but could be slightly more structured by separating pagination and filtering details.

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 lack of an output schema and no usage guidelines, the description is adequate but not complete. It covers the basic behavior but omits crucial context about when to choose this tool over siblings.

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 fully documents all four parameters. The description only lists parameter names without adding meaning beyond what is already available, meeting the baseline for high-coverage schemas.

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 and resource ('List all users for the tenant'), making its purpose immediately clear. It is distinguishable from write-oriented siblings like create_user or update_user.

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?

No guidance is provided on when to use this tool versus alternatives. It fails to mention sibling tools like scim_list_users or scim_get_user, leaving the agent to infer the correct context.

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