Skip to main content
Glama

auth_users_list

Read-onlyIdempotent

List end-user accounts of your app — the people who signed up via auth_signup. Distinct from project_list (your own projects). Returns id, email, display_name, email_verified, created_at, last_login_at. Paginated by created_at descending.

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": {
      "project_id": "<project_id>"
    },
    "name": "auth_users_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 50, max 200)
cursorNoPagination cursor from a previous response
searchNoOptional case-insensitive email substring filter
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description still adds useful behavior beyond them by enumerating returned fields and stating the default sort order ('paginated by created_at descending'). It doesn't mention auth/permission requirements or result-size limits, which would have pushed this higher.

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 short sentences, front-loaded with the resource identity, then the sibling distinction, then return shape, then pagination. Every sentence carries distinct information and nothing is repeated from the schema.

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?

With no output schema, the description correctly compensates by listing the returned fields, and it covers pagination behavior for a paginated list tool. Minor gaps remain around filtering/pagination interaction (whether `search` applies before the created_at cursor ordering) and permissions, but nothing critical for a correct call.

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 description coverage is 100%, so limit, cursor, search, and project_id are already fully documented, including the server-side resolution and 'default' fallback. The description only contributes the ordering used by the cursor, which is a marginal addition rather than new parameter meaning.

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 end-user accounts of your app'), ties them to their origin ('the people who signed up via auth_signup'), and explicitly contrasts with the nearest-looking sibling: 'Distinct from `project_list` (your own projects).' An agent can disambiguate without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear selection rule by naming `project_list` as the alternative and explaining the difference (end users vs. your own projects), plus context that these accounts come from `auth_signup`. It stops short of explicit when-not-to-use cases (e.g. looking up a single user or searching across other resources).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources