Skip to main content
Glama
DynamicEndpoints

pocketbase-mcp-server

list_records

Fetch and display records from PocketBase databases using the MCP protocol. This tool simplifies data retrieval and supports efficient database interactions within the pocketbase-mcp-server ecosystem.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary registration and handler for the 'list_records' tool in the main PocketBase MCP server. Defines input schema using Zod and implements the PocketBase getList query.
    server.tool(
      'list_records',
      {
        collection: z.string().describe('Collection name'),
        filter: z.string().optional().describe('Filter query'),
        sort: z.string().optional().describe('Sort field and direction'),
        page: z.number().optional().describe('Page number'),
        perPage: z.number().optional().describe('Items per page')
      },
      async ({ collection, filter, sort, page = 1, perPage = 50 }) => {
        try {
          const options: any = {};
          if (filter) options.filter = filter;
          if (sort) options.sort = sort;
    
          const result = await this.pb.collection(collection).getList(page, perPage, options);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          return {
            content: [{ type: 'text', text: `Failed to list records: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Handler function listRecords in the worker-compatible PocketBase MCP agent, called from the tool dispatch switch statement.
    private async listRecords(collection: string, options: any = {}) {
      if (!this.pb) {
        throw new Error('PocketBase not configured');
      }
    
      try {
        const records = await this.pb.collection(collection).getList(
          options.page || 1,
          options.perPage || 30,
          {
            filter: options.filter,
            sort: options.sort
          }
        );
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(records, null, 2)
            }
          ]
        };
      } catch (error: any) {
        throw new Error(`Failed to list records: ${error.message}`);
      }
    }
  • Input schema definition for the list_records tool in the ListTools response of the worker-compatible agent.
      name: "list_records",
      description: "List records from a collection",
      inputSchema: {
        type: "object",
        properties: {
          collection: {
            type: "string",
            description: "Collection name"
          },
          page: {
            type: "number",
            description: "Page number (default: 1)"
          },
          perPage: {
            type: "number",
            description: "Records per page (default: 30)"
          },
          filter: {
            type: "string",
            description: "Filter expression"
          },
          sort: {
            type: "string",
            description: "Sort expression"
          }
        },
        required: ["collection"]
      }
    },
  • Registration and inline handler for list_records tool in the Cloudflare Agent implementation of PocketBase MCP server.
    this.server.tool(
      "list_records",
      "List records from a collection with optional filtering and pagination",
      {
        collection: z.string().describe('Collection name'),
        page: z.number().optional().default(1).describe('Page number'),
        perPage: z.number().optional().default(30).describe('Records per page'),
        sort: z.string().optional().describe('Sort order (e.g., "-created")'),
        filter: z.string().optional().describe('Filter expression'),
        expand: z.string().optional().describe('Relations to expand')
      },
      async ({ collection, page, perPage, sort, filter, expand }) => {
        if (!this.pb) {
          throw new Error('PocketBase not initialized');
        }
    
        const records = await this.pb.collection(collection).getList(page, perPage, {
          sort,
          filter,
          expand
        });
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(records, null, 2)
          }]
        };
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicEndpoints/pocketbase-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server