Skip to main content
Glama
ricleedo

MCP Server Boilerplate

by ricleedo

mongo-delete-document

Delete documents from MongoDB collections using query filters. Specify database, collection, and filter criteria to remove single or multiple documents as needed.

Instructions

Delete documents from a MongoDB collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseYesDatabase name
collectionYesCollection name
filterYesQuery filter to match documents to delete
deleteManyNoWhether to delete multiple documents (default: false)

Implementation Reference

  • The asynchronous handler function that connects to the MongoDB database, retrieves the specified collection, executes deleteOne or deleteMany based on the provided filter and optional deleteMany flag, and returns a text content response indicating the number of deleted documents.
    async ({ database: dbName, collection: collectionName, filter, deleteMany = false }) => {
      try {
        const db = await ensureConnection(dbName);
        const collection: Collection = db.collection(collectionName);
        
        const result = deleteMany
          ? await collection.deleteMany(filter)
          : await collection.deleteOne(filter);
        
        return {
          content: [
            {
              type: "text",
              text: `Delete operation completed. Deleted ${result.deletedCount} document(s)`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to delete document(s): ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Zod schema for input validation: requires database name, collection name, and filter object; optional deleteMany boolean to control single or multiple deletion.
    {
      database: z.string().describe("Database name"),
      collection: z.string().describe("Collection name"),
      filter: z.record(z.any()).describe("Query filter to match documents to delete"),
      deleteMany: z.boolean().optional().describe("Whether to delete multiple documents (default: false)"),
    },
  • src/index.ts:201-231 (registration)
    The server.tool() call that registers the 'mongo-delete-document' tool with the MCP server, providing name, description, input schema, and handler function.
    server.tool(
      "mongo-delete-document",
      "Delete documents from a MongoDB collection",
      {
        database: z.string().describe("Database name"),
        collection: z.string().describe("Collection name"),
        filter: z.record(z.any()).describe("Query filter to match documents to delete"),
        deleteMany: z.boolean().optional().describe("Whether to delete multiple documents (default: false)"),
      },
      async ({ database: dbName, collection: collectionName, filter, deleteMany = false }) => {
        try {
          const db = await ensureConnection(dbName);
          const collection: Collection = db.collection(collectionName);
          
          const result = deleteMany
            ? await collection.deleteMany(filter)
            : await collection.deleteOne(filter);
          
          return {
            content: [
              {
                type: "text",
                text: `Delete operation completed. Deleted ${result.deletedCount} document(s)`,
              },
            ],
          };
        } catch (error) {
          throw new Error(`Failed to delete document(s): ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • Helper function to establish and cache MongoDB client connection and database instances, used by the tool handler to access the database.
    async function ensureConnection(dbName: string): Promise<Db> {
      if (!mongoClient) {
        const uri = getMongoUri();
        mongoClient = new MongoClient(uri);
        await mongoClient.connect();
      }
      
      if (!databases.has(dbName)) {
        databases.set(dbName, mongoClient.db(dbName));
      }
      
      return databases.get(dbName)!;
    }
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 critical behavioral traits such as whether deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure (e.g., return values or errors).

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 waste. It's front-loaded and appropriately sized for the tool's complexity, 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 destructive tool with no annotations and no output schema, the description is incomplete. It lacks context on safety (e.g., irreversible deletion), error handling, or what to expect after invocation, which is crucial for an AI agent to use it correctly.

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 all parameters. The description adds no additional meaning beyond what's in the schema, such as examples of filter usage or implications of 'deleteMany'. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Delete') and resource ('documents from a MongoDB collection'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'mongo-update-document' or 'mongo-create-document' beyond the action name, missing explicit sibling distinction.

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. It doesn't mention prerequisites like authentication, when to choose 'deleteMany' over single deletion, or how it compares to siblings like 'mongo-update-document' for partial modifications.

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/ricleedo/mongo-boilerplate-mcp'

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