Skip to main content
Glama
Vijayakumar-DevOps

MongoDB MCP Server

update-many

Update all documents that match a filter in a MongoDB collection, applying update operators to multiple records in one operation. Include upsert to insert if no match.

Instructions

Updates all documents that match the specified filter for a collection. If the list of documents is above com.mongodb/maxRequestPayloadBytes, consider updating them in batches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoThe selection criteria for the update, matching the syntax of the filter argument of db.collection.updateOne()
updateYesAn update document describing the modifications to apply using update operator expressions
upsertNoControls whether to insert a new document if no documents match the filter
databaseYesDatabase name
collectionYesCollection name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseYes
collectionYes
upsertedIdNo
matchedCountYes
modifiedCountYes
upsertedCountYes
Behavior3/5

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

The description adds the batching consideration, which is a useful operational detail. However, it does not disclose other behavioral traits such as the potentially large scope of updates, atomicity, or irreversibility, which are relevant for a mutation tool. The annotations already indicate it is not read-only, so the description adds moderate context.

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 two sentences: the first clearly states the core action, and the second adds a useful operational tip. There is no redundancy or wasted wording.

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

Completeness4/5

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

The description, combined with the thoroughly documented input schema and presence of an output schema, provides sufficient context for basic use. It covers the main behavior and includes a batching tip. Minor gaps exist (e.g., not mentioning atomicity or side effects), but these are not critical given the schema completeness.

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?

The input schema already covers all parameters with 100% description coverage, so the schema carries the burden. The description does not add any parameter-specific semantics beyond what is in the schema, earning the baseline score of 3.

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

Purpose5/5

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

The description clearly states the tool updates all documents matching a filter in a collection, using the specific verb 'Updates' and identifying the resource. This distinguishes it from sibling tools like delete-many, find, and insert-many.

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

Usage Guidelines3/5

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

The description provides a practical guideline about batching updates when the payload exceeds a size limit, implying when to use this tool. However, it does not explicitly mention alternatives or when to prefer this over similar tools, leaving usage context partially implicit.

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/Vijayakumar-DevOps/mongo-mcp-1.14.0'

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