Skip to main content
Glama
datastax

Astra DB MCP Server

Official

BulkUpdateRecords

Update multiple records within a specified collection simultaneously using ID-based data modifications, streamlining batch operations for Astra DB databases.

Instructions

Update multiple records in a collection at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNameYesName of the collection containing the records
recordsYesArray of records to update with their IDs

Implementation Reference

  • The core handler function that executes bulk updates on records in an Astra DB collection, preferring bulkWrite for efficiency or falling back to individual updates, returning the update count and success message.
    export async function BulkUpdateRecords({
      collectionName,
      records,
    }: BulkUpdateRecordsArgs): Promise<BulkUpdateRecordsResult> {
      const collection: Collection = db.collection(collectionName);
      
      // Create an array of update operations for bulkWrite
      const updateOperations = records.map(({ id, record }) => ({
        updateOne: {
          filter: { _id: id },
          update: { $set: record }
        }
      }));
      
      let updatedCount = 0;
      
      try {
        // Try to use bulkWrite for better performance
        if (typeof collection.bulkWrite === 'function') {
          // Use bulkWrite for batch processing
          const result = await collection.bulkWrite(updateOperations);
          
          // Get the count of modified documents
          updatedCount = result.modifiedCount || 0;
        } else {
          // Fallback to individual updateOne operations
          for (const { id, record } of records) {
            const result = await collection.updateOne({ _id: id }, { $set: record });
            if (result.modifiedCount) {
              updatedCount += result.modifiedCount;
            }
          }
        }
      } catch (error) {
        console.error("Error in bulk update:", error);
        throw error;
      }
      
      return {
        message: `Successfully updated ${updatedCount} records`,
        updatedCount,
      };
    }
  • JSON Schema definition for the BulkUpdateRecords tool input parameters used in MCP tool listing and validation.
    {
      name: "BulkUpdateRecords",
      description: "Update multiple records in a collection at once",
      inputSchema: {
        type: "object",
        properties: {
          collectionName: {
            type: "string",
            description: "Name of the collection containing the records",
          },
          records: {
            type: "array",
            description: "Array of records to update with their IDs",
            items: {
              type: "object",
              properties: {
                id: {
                  type: "string",
                  description: "ID of the record to update",
                },
                record: {
                  type: "object",
                  description: "The updated record data",
                },
              },
              required: ["id", "record"],
            },
          },
        },
        required: ["collectionName", "records"],
      },
    },
  • index.ts:317-332 (registration)
    Dispatches the CallToolRequest for BulkUpdateRecords by invoking the handler function and formatting the response for MCP.
    case "BulkUpdateRecords":
      const bulkUpdateResult = await BulkUpdateRecords({
        collectionName: args.collectionName as string,
        records: args.records as Array<{
          id: string;
          record: Record<string, any>;
        }>,
      });
      return {
        content: [
          {
            type: "text",
            text: bulkUpdateResult.message,
          },
        ],
      };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Update multiple records') but lacks critical details: whether this is atomic/transactional, what happens on partial failures, permission requirements, rate limits, or return format. For a mutation tool with zero annotation coverage, this leaves significant behavioral unknowns.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and immediately communicates the bulk nature. Every word earns its place, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context: success/failure behavior, error handling, authentication needs, or what the tool returns. Given the complexity of bulk operations and lack of structured safety information, more behavioral disclosure is needed.

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 fully documents both parameters (collectionName, records). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain format expectations, constraints, or examples. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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

Purpose4/5

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

The description clearly states the verb ('Update') and resource ('multiple records in a collection'), making the purpose immediately understandable. It distinguishes from single-record updates (UpdateRecord) by specifying 'multiple records at once', but doesn't explicitly differentiate from other bulk operations like BulkCreateRecords or BulkDeleteRecords beyond the action verb.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., existing records/collections), compare to UpdateRecord for single updates, or explain when bulk updates are appropriate versus individual operations. The agent must infer usage from the name and context alone.

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/datastax/astra-db-mcp'

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