Skip to main content
Glama
Sign In
pocketbase-mcp

pocketbase-mcp

by nestebe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List external auth providers

list_external_auths

Find all OAuth2 providers linked to a user record. Provide the record ID and optional auth collection to list external auths; requires superuser access.

Instructions

List the OAuth2 providers linked to a specific user record (superuser only).

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": {
      "recordId": "<recordId>"
    },
    "name": "list_external_auths"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYesUser record id.
collectionNoAuth collection (default 'users').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose an important constraint ('superuser only') and the targeted resource, but it does not describe return shape or error behavior. For a simple read-only list tool, this is acceptable but not rich.

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?

A single sentence conveys the action, target, and access restriction without wasted words. The scope is front-loaded and the permission qualifier is placed clearly.

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 two-parameter list tool, the description provides enough context to invoke it correctly: what it lists, for whom, and who may use it. The absence of an output schema is mitigated by the obvious meaning of 'List', though a bit more detail on the returned data would make it fully complete.

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 the schema already documents both parameters. The description adds no extra parameter-level meaning, so the baseline 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?

Description uses a specific verb ('List') and a precise resource ('OAuth2 providers linked to a specific user record'), which clearly distinguishes it from sibling tools like unlink_external_auth and list_auth_methods. The 'superuser only' qualifier adds a useful access scope.

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?

The description gives clear context: use this to list external OAuth providers for a specific user, and only as a superuser. It does not explicitly name alternatives or exclusions, but its scope is clear enough to guide selection.

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