Skip to main content
Glama
DynamicEndpoints

Advanced PocketBase MCP Server

create_record

Add new entries to PocketBase collections by specifying field values and collection names to store structured data in the database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Worker-compatible implementation of the create_record tool handler. Calls PocketBase.collection(collection).create(data) to create the record and returns JSON response.
    /**
     * Create a new record
     */
    private async createRecord(collection: string, data: any) {
      if (!this.pb) {
        throw new Error('PocketBase not configured');
      }
    
      try {
        const record = await this.pb.collection(collection).create(data);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(record, null, 2)
            }
          ]
        };
      } catch (error: any) {
        throw new Error(`Failed to create record: ${error.message}`);
      }
    }
  • Registration of create_record tool in the switch statement within CallToolRequestHandler.
    case "create_record": {
      if (!args || typeof args !== "object" || typeof (args as any).collection !== "string" || typeof (args as any).data !== "object") {
        throw new Error("'collection' (string) and 'data' (object) are required for create_record");
      }
      return await this.createRecord((args as any).collection, (args as any).data);
    }
  • Input schema definition for create_record tool in the list tools response.
    name: "create_record",
    description: "Create a new record in a collection",
    inputSchema: {
      type: "object",
      properties: {
        collection: {
          type: "string",
          description: "Collection name"
        },
        data: {
          type: "object",
          description: "Record data"
        }
      },
      required: ["collection", "data"]
    }
  • Inline handler for create_record in Cloudflare agent. Directly calls PocketBase create and updates state.
    async ({ collection, data }) => {
      if (!this.pb) {
        throw new Error('PocketBase not initialized');
      }
    
      const record = await this.pb.collection(collection).create(data);
      
      // Update activity time
      this.setState({
        ...this.state,
        lastActivityTime: Date.now()
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(record, null, 2)
        }]
      };
    }
  • Full registration of create_record tool including schema and inline handler in Cloudflare agent.
    // Create record
    this.server.tool(
      "create_record",
      "Create a new record in a collection",
      {
        collection: z.string().describe('Collection name'),
        data: z.record(z.any()).describe('Record data')
      },
      async ({ collection, data }) => {
        if (!this.pb) {
          throw new Error('PocketBase not initialized');
        }
    
        const record = await this.pb.collection(collection).create(data);
        
        // Update activity time
        this.setState({
          ...this.state,
          lastActivityTime: Date.now()
        });
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(record, 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

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/advanced-pocketbase-mcp-server'

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