Skip to main content
Glama
Sign In
pocketbase-mcp

pocketbase-mcp

by nestebe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get full record list

get_full_record_list

Fetch all records matching a filter with automatic pagination, ideal for exports or small to medium collections. Use paginated listing for large datasets to avoid oversized responses.

Instructions

Fetch ALL records matching a filter, auto-paginating in batches. Use for exports or small/medium collections. Prefer list_records with pagination for large datasets to avoid huge responses.

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": "get_full_record_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort expression.
batchNoRecords per underlying request (default 200).
expandNoComma-separated relations to expand.
fieldsNoComma-separated fields to return.
filterNoPocketBase filter expression.
collectionYesCollection id or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses auto-pagination, batched fetching, and the risk of huge responses. It does not mention error behavior, auth needs, or response format, but the read-only nature is clearly implied by 'Fetch'.

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?

Two sentences with no filler. The purpose and key behavioral trait are front-loaded, and the usage guidance is packed into the second sentence without waste.

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 read-only fetch tool with fully documented parameters and clear usage boundaries, the description is mostly complete. The absence of an output schema is mitigated by the obvious return type (records), and the warning about large responses covers the main operational risk.

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 all six parameters. The description adds contextual hints about filters and batches but does not materially improve on the schema's per-parameter descriptions. Baseline 3 is appropriate.

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 specific verb ('Fetch'), a clear resource ('ALL records'), and a distinguishing behavior ('auto-paginating in batches'). It also differentiates this tool from the paginated list_records sibling by emphasizing the 'ALL records' scope.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('exports or small/medium collections') and gives a direct alternative ('Prefer list_records with pagination for large datasets'). This gives an agent clear selection criteria.

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