Skip to main content
Glama

Batch Update Entries

batch_update_entries

Update multiple existing journal entries in a single transaction, up to 50 per batch, to keep project memory changes consistent and atomic.

Instructions

Update multiple existing journal entries in a single transaction. Max 50 per batch. REQUIRED: You MUST include project_number. Extract this by querying memory://agent-id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "batch_update_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesNo
auto_indexNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
project_numberNoNumeric project ID applied to batch updates when omitted per item.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
countNo
errorNoHuman-readable error message
detailsNoAdditional error context
successNo
updatedNo
categoryNoError category (validation, query, connection, internal)
notFoundNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
indexStatusesNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • addedInput schema / properties / project_number
      Added value: +{
      +  "description": "Numeric project ID applied to batch updates when omitted per item.",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • changedInput schema / properties / updates / items / properties / content / description
      Previous value: -"Updated markdown content. Preserve the existing ## section header structure. For session summaries, keep the ## Accomplished / ## Unfinished / Blocked / ## Context for Next Session structure intact. Do NOT restructure or add new top-level sections unless explicitly requested."New value: +"Updated markdown content. Preserve the existing ## section header structure. For session summaries, keep the ## Accomplished / ## Unfinished / Blocked / ## Context for Next Session / ## Commits structure intact. Do NOT restructure or add new top-level sections unless explicitly requested."
    • addedInput schema / properties / updates / items / properties / target_workspace_id
      Added value: +{
      +  "description": "Target workspace to move entry into (e.g. \"mysql-mcp\")",
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already disclose the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real value beyond them: atomic 'single transaction' semantics, a hard batch ceiling of 50, and the required project_number precondition. It stops short of saying whether a mid-batch failure rolls back the whole transaction or what error surface to expect.

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?

Three short sentences, front-loaded with the action and atomicity, then the batch limit, then the precondition. No filler or repetition.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the transactional framing plus batch cap cover the core operation. But for a tool taking a large heterogeneous update array with 50% schema coverage, the description gives no guidance on which item fields are mutable or how to resolve the required-vs-optional conflict on project_number.

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 coverage is 50% and the 20+ fields inside the nested 'updates' items are almost entirely undocumented, so the description would need to compensate but does not. Worse, it declares project_number 'REQUIRED: You MUST include', while the schema lists required: [] and describes project_number as an optional fallback ('applied to batch updates when omitted per item'); that conflict will confuse an agent. Positive addition: the pointer to memory://agent-id for obtaining the value.

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?

States a specific verb and resource ('Update multiple existing journal entries') plus the transactional scope ('in a single transaction'), which clearly separates it from single-record update_entry. It does not name the near-identical siblings team_batch_update_entries or batch_create_entries, so an agent cannot fully disambiguate from the name alone.

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?

Gives a concrete operational constraint (max 50 per batch) and a mandatory precondition (project_number). However, it never states when to prefer this over update_entry for a single item or over batch_create_entries / team_batch_update_entries, so alternative selection is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools