Skip to main content
Glama

bulk_update_records

Update a field (or fields) in many records at once. Instead of N update_record calls for 'set status Processed on all of today's orders'. Records can be chosen by a list of IDs, by a filter (field = value), by a report, or all records of the form. Supports action rules — triggers fire as on an ordinary update.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>",
      "entity_id": "<entity_id>",
      "fields_to_set": "<fields_to_set>"
    },
    "name": "bulk_update_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
filterNoFilter by one field: {field: "Field name", value: "value"}. For example: {field: "Status", value: "New"}
entity_idYesForm ID (from list_forms or describe_project)
report_idNoReport/filter ID — updates only the records in this report
record_idsNoThe specific record IDs to update. If not given, filter or report_id or all records are used.
fields_to_setYesFields to update: {"Field name" or field_id: "new value"}. For example: {"Status": "Processed", "Priority": "Low"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / fields_to_set / description
      Previous value: -"Поля для оновлення: {\"Назва поля\" або field_id: \"нове значення\"}. Наприклад: {\"Статус\": \"Оброблено\", \"Пріоритет\": \"Низький\"}"New value: +"Fields to update: {\"Field name\" or field_id: \"new value\"}. For example: {\"Status\": \"Processed\", \"Priority\": \"Low\"}"
    • changedInput schema / properties / filter / description
      Previous value: -"Фільтр по одному полю: {field: \"Назва поля\", value: \"значення\"}. Наприклад: {field: \"Статус\", value: \"Новий\"}"New value: +"Filter by one field: {field: \"Field name\", value: \"value\"}. For example: {field: \"Status\", value: \"New\"}"
    • changedInput schema / properties / filter / properties / field / description
      Previous value: -"Назва або ID поля"New value: +"Field name or ID"
    • changedInput schema / properties / filter / properties / value / description
      Previous value: -"Значення для пошуку"New value: +"Value to search for"
    • changedInput schema / properties / record_ids / description
      Previous value: -"Конкретні ID записів для оновлення. Якщо не вказано — використовується filter або report_id або всі записи."New value: +"The specific record IDs to update. If not given, filter or report_id or all records are used."
    • changedInput schema / properties / report_id / description
      Previous value: -"ID звіту/фільтру — оновить тільки записи що входять в цей звіт"New value: +"Report/filter ID — updates only the records in this report"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds a non-obvious behavioral trait: 'Supports action rules — triggers fire as on an ordinary update,' which informs the agent about side effects not captured by annotations. It does not discuss failure modes or permission requirements, but the action-rule note is a valuable addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action, then gives a concrete example, then explains record selection and action rules. Every sentence contributes useful information and there is no filler.

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?

Given the annotations covering safety and the 100% schema coverage, the description provides enough context to use the tool correctly: it clarifies the bulk nature, selection mechanisms, and trigger side effects. Minor gaps like error handling and permission requirements are acceptable given the structured fields already present.

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 100%, so every parameter is already documented. The description mentions the selection methods (IDs, filter, report) and the fields_to_set intent, but adds no syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Update a field (or fields) in many records at once.' It explicitly contrasts with the sibling update_record by noting 'Instead of N update_record calls,' making the distinction immediately clear.

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

Usage Guidelines4/5

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

It provides clear usage context by explaining the batch alternative to repeated update_record calls and lists the ways records can be selected (IDs, filter, report, or all records). It stops short of explicitly stating when not to use it or naming other alternatives like update_cell, but the intended use case is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources