Skip to main content
Glama
andrewlwn77
by andrewlwn77

update_record

Modify specific fields in a database record by providing the base ID, table name, record ID, and updated data values.

Instructions

Update a single record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project
table_nameYesThe name of the table
record_idYesThe ID of the record to update
dataYesThe fields to update

Implementation Reference

  • The handler function for the 'update_record' MCP tool. It invokes the NocoDB client's updateRecord method with the provided base_id, table_name, record_id, and data, then returns the updated record along with a success message.
    handler: async (
      client: NocoDBClient,
      args: {
        base_id: string;
        table_name: string;
        record_id: string;
        data: any;
      },
    ) => {
      const record = await client.updateRecord(
        args.base_id,
        args.table_name,
        args.record_id,
        args.data,
      );
      return {
        record,
        message: "Record updated successfully",
      };
    },
  • The input schema defining the parameters for the 'update_record' tool: base_id (string), table_name (string), record_id (string), and data (object). All are required.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "The ID of the base/project",
        },
        table_name: {
          type: "string",
          description: "The name of the table",
        },
        record_id: {
          type: "string",
          description: "The ID of the record to update",
        },
        data: {
          type: "object",
          description: "The fields to update",
          additionalProperties: true,
        },
      },
      required: ["base_id", "table_name", "record_id", "data"],
    },
  • src/index.ts:55-62 (registration)
    Registers the 'update_record' tool by including the recordTools array (which defines update_record) into the allTools array. This allTools is used in MCP handlers for listing tools (ListToolsRequestSchema) and executing them (CallToolRequestSchema).
    const allTools = [
      ...databaseTools,
      ...tableTools,
      ...recordTools,
      ...viewTools,
      ...queryTools,
      ...attachmentTools,
    ];
  • The NocoDBClient.updateRecord helper method called by the tool handler. It resolves the table ID and primary key field, then performs a PATCH request to the NocoDB API to update the specified record.
    async updateRecord(
      baseId: string,
      tableName: string,
      recordId: string,
      data: NocoDBRecord,
    ): Promise<NocoDBRecord> {
      // First get table ID from table name
      const tables = await this.listTables(baseId);
      const table = tables.find(
        (t) => t.table_name === tableName || t.title === tableName,
      );
      if (!table) {
        throw new NocoDBError(`Table ${tableName} not found`);
      }
    
      // Get the primary key field name (usually ID but can vary)
      const columns = await this.listColumns(table.id);
      const pkColumn =
        columns.find((col) => col.pk) ||
        columns.find((col) => col.title === "ID");
      const pkField = pkColumn?.title || "ID";
    
      const response = await this.client.patch(
        `/api/v2/tables/${table.id}/records`,
        {
          [pkField]: recordId,
          ...data,
        },
      );
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether updates are partial or full, if there are validation rules, rate limits, authentication needs, or what happens on failure. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is extremely concise with a single sentence, 'Update a single record', which is front-loaded and wastes no words. Every word earns its place, though this brevity contributes to gaps in other dimensions.

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

Completeness2/5

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

Given the complexity of a mutation tool with 4 required parameters, no annotations, and no output schema, the description is incomplete. It fails to explain return values, error conditions, or operational context, leaving significant gaps for an AI agent to understand how to use it effectively.

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 input schema fully documents all 4 parameters. The description adds no additional meaning beyond what's in the schema, such as explaining the structure of 'data' or relationships between parameters. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Update a single record' clearly states the action (update) and resource (record), but it's vague about scope and doesn't differentiate from siblings like 'insert_record' or 'delete_record'. It lacks specificity about what constitutes a 'record' in this context.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'insert_record' for creating new records or 'delete_record' for removal. The description doesn't mention prerequisites, such as needing an existing record ID, or contextual factors like permissions or constraints.

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/andrewlwn77/nocodb-mcp'

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