Skip to main content
Glama
DynamicEndpoints

pocketbase-mcp-server

list_collections

Retrieve and manage all collections within a PocketBase database using this tool. Simplify schema review, data organization, and operational workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler and registration for the 'list_collections' tool in the core MCP server. Fetches collections using getList(1, 100), filters system collections optionally, and returns formatted JSON.
    server.tool(
      'list_collections',
      {
        includeSystem: z.boolean().optional().default(false).describe('Whether to include system collections')
      },
      async ({ includeSystem }) => {
        try {
          const collections = await this.pb.collections.getList(1, 100);
          const filteredCollections = includeSystem
            ? collections.items
            : collections.items.filter((c: any) => !c.system);
    
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(filteredCollections.map((c: any) => ({
                id: c.id,
                name: c.name,
                type: c.type,
                system: c.system,
                recordCount: c.recordCount || 0
              })), null, 2)
            }]
          };
        } catch (error: any) {
          return {
            content: [{ type: 'text', text: `Failed to list collections: ${error.message}` }],
            isError: true
          };
        }
      }
  • Handler implementation in Cloudflare agent variant using getFullList() and returns full JSON of all collections.
    "list_collections",
    "List all collections in the PocketBase database",
    {},
    async () => {
      if (!this.pb) {
        throw new Error('PocketBase not initialized. Please configure POCKETBASE_URL.');
      }
    
      const collections = await this.pb.collections.getFullList();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(collections, null, 2)
        }]
      };
    }
  • Handler in simple agent using getFullList() with initialization check.
    'list_collections',
    {
      description: 'List all collections in the PocketBase database'
    },
    async () => {
      await this.ensureInitialized();
      if (!this.pb) {
        throw new Error('PocketBase not initialized');
      }
    
      try {
        const collections = await this.pb.collections.getFullList();
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(collections, null, 2)
          }]
        };
      } catch (error: any) {
        throw new Error(`Failed to list collections: ${error.message}`);
      }
    }
  • Dedicated helper function listCollections() used in switch case for tool handling in worker-compatible agent.
    private async listCollections() {
      if (!this.pb) {
        throw new Error('PocketBase not configured');
      }
    
      try {
        const collections = await this.pb.collections.getFullList();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(collections, null, 2)
            }
          ]
        };
      } catch (error: any) {
        throw new Error(`Failed to list collections: ${error.message}`);
      }
    }
  • Tool registration in listTools handler for worker-compatible agent, defining schema as empty object.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "health_check",
            description: "Check the health status of the MCP server",
            inputSchema: {
              type: "object",
              properties: {},
              required: []
            }
          },
          {
            name: "list_collections",
            description: "List all PocketBase collections",
            inputSchema: {
              type: "object",
              properties: {},
              required: []
            }
          },
          {
            name: "get_collection",
            description: "Get detailed information about a specific collection",
            inputSchema: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "Collection name"
                }
              },
              required: ["name"]
            }
          },
          {
            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",
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