pocketbase-mcp

List records

list_records

Fetch paginated records from a PocketBase collection with filtering, sorting, and relation expansion. Skip total count to speed up queries.

Instructions

List records of a collection with pagination, filtering, sorting and relation expansion. Filter supports operators like =, !=, >, <, ~ (contains), and functions. Example filter: 'status = "active" && created > "2024-01-01"'. Use expand to inline related records (e.g. 'author,comments_via_post'). Set skipTotal to true for faster queries when you don't need the total count.

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": {
      "collection": "<collection>"
    },
    "name": "list_records"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default 1).
`sort`	No	Sort expression, e.g. '-created,title'.
`expand`	No	Comma-separated relations to expand.
`fields`	No	Comma-separated fields to return (supports :excerpt modifiers).
`filter`	No	PocketBase filter expression.
`perPage`	No	Items per page (default 30).
`skipTotal`	No	Skip counting total items for performance.
`collection`	Yes	Collection id or name.

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 present, so the description carries the full burden. It discloses filter operators, expand behavior, and the skipTotal performance trade-off, but does not mention the response envelope, authentication needs, or error behavior.

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 core purpose is front-loaded in the first sentence, with each following sentence adding concrete, non-redundant examples. It is compact without being terse.

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?

For a read tool with 8 parameters and no output schema, the description covers query mechanics well but omits the return shape and any guidance about when to prefer sibling listing tools. This leaves some ambiguity for an agent deciding how to handle the response.

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 description coverage is 100%, so the baseline is 3. The description adds real value beyond the schema by showing exact filter expression syntax, operators, expand syntax, and the skipTotal optimization rationale.

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 records of a collection') and names the key capabilities: pagination, filtering, sorting, and relation expansion. This clearly distinguishes it from single-record siblings like get_record or get_first_record.

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?

Provides practical usage tips (expand syntax, skipTotal for performance), which implies when the tool is useful. However, it never explicitly contrasts with alternatives like get_full_record_list or get_record, nor says when not to use this tool.

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

Deploy Server