pocketbase-mcp

List superusers

list_superusers

Fetch superuser (admin) accounts from the _superusers collection. Supports pagination, sorting, and filtering to pinpoint specific administrators.

Instructions

List superuser (admin) accounts from the built-in _superusers collection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_superusers"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default 1).
`sort`	No	Sort expression, e.g. '-created'.
`filter`	No	Filter expression, e.g. 'email ~ "@example.com"'.
`perPage`	No	Items per page (default 100).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. The word 'List' clearly implies a read-only operation, and 'built-in _superusers collection' adds useful context, but the description does not disclose return format, pagination behavior, or any access requirements beyond what the schema already implies.

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?

The description is a single focused sentence with no filler. It front-loads the action and target, then adds the useful source-collection detail, making it easy to parse quickly.

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 paginated-list tool with no output schema, the description conveys enough to invoke it correctly: the action, the resource, and the source collection. It does not enumerate return fields, but 'List superuser accounts' reasonably implies the response contains those accounts.

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?

The input schema already documents all four parameters with meaningful descriptions (page, sort, filter, perPage), achieving 100% schema description coverage. The tool description adds no additional parameter semantics, so the baseline score of 3 applies.

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 states a precise verb ('List') and resource ('superuser (admin) accounts'), and clarifies the data source ('built-in _superusers collection'). This distinguishes it from sibling tools like create_superuser, update_superuser, delete_superuser, and list_external_auths.

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?

Usage is implied: the agent can infer that this tool should be used when superuser accounts need to be listed. However, there is no explicit guidance about when not to use it or which sibling tool to use for related operations such as creating or updating superusers.

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

Deploy Server