Skip to main content
Glama

Settings Set Batch

settings_set_batch
Destructive

Update settings for multiple components on one page in one all-or-nothing write, aborting the batch if any change is refused. Preview with dry_run before applying.

Instructions

settings_set for many components of one page in ONE write: each item is {component_id, changes} (changes exactly as for settings_set). Much faster than one settings_set per component (one read-back and editor reload in total). All or nothing: any refused change aborts the batch with nothing written. page_get fingerprint; journalled; operation_restore undoes it.

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": {
      "page_id": "<page_id>",
      "components": "<components>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "settings_set_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
page_idYes
report_idNo
componentsYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag it as a destructive write, but the description adds real behavioral context beyond them: atomic all-or-nothing semantics ('any refused change aborts the batch with nothing written'), the fingerprint precondition, journaling, and a named undo path (operation_restore). It omits that dry_run defaults to true, which matters for an agent deciding whether this call actually writes.

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?

Front-loads the core distinction ('ONE write') and then compresses payload shape, performance rationale, atomicity, and undo into four short clauses with no filler. The telegraphic style ('page_get fingerprint; journalled; operation_restore undoes it.') is dense but readable.

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 output schema exists, so return values needn't be described, and the description covers the parts that matter most for a destructive batch: atomicity, the required precondition, and recoverability. The gap is the unmentioned dry_run default, which leaves an agent unsure whether calling it commits or previews.

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 0% and there are five parameters, so the description must carry the load. It explains the components item shape and the fingerprint's origin (page_get), but leaves dry_run and report_id entirely unexplained despite dry_run gating whether anything is written.

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?

States a specific verb (settings_set), an explicit batch scope ('many components of one page in ONE write'), and structures the payload as {component_id, changes}. It is cleanly distinguished from the sibling settings_set by the one-call-per-page framing.

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?

Gives a comparative rule for when to prefer this over repeated settings_set calls ('much faster... one read-back and editor reload in total') and implies the single-call sibling for the one-component case. No explicit when-not-to-use case or prerequisite section, but the selection logic is derivable.

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