Skip to main content
Glama

batch_patch_content

Destructive

patch_content on multiple keys; all-or-nothing validation. Preferred edit path for pages over 60KB. replace-string value/replace ≤60KB; whole call ≤80KB.

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": {
      "site": "<site>",
      "items": "<items>"
    },
    "name": "batch_patch_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug, e.g. acme-studio
itemsYes
contextNoWhy you're calling this (activity log).
guestTokenNoGuest token from start_site (pgg_…). Omit when signed in with OAuth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • changedInput schema / properties / guestToken / description
      Previous value: -"Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy."New value: +"Guest token from start_site (pgg_…). Omit when signed in with OAuth."
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "items",
      -  "context"
      -]New value: +[
      +  "site",
      +  "items"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / ops / items / properties / anchored
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed6 schema fields changed
    • addedInput schema / properties / items / items / properties / ops / items / properties / attrs
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / items / items / properties / ops / items / properties / op / enum
      Previous value: -[
      -  "set-attr",
      -  "remove-attr",
      -  "replace-text",
      -  "remove-node",
      -  "insert-after",
      -  "replace-inner-html",
      -  "replace-outer-html",
      -  "replace-string"
      -]New value: +[
      +  "set-attr",
      +  "remove-attr",
      +  "replace-text",
      +  "remove-node",
      +  "insert-after",
      +  "replace-inner-html",
      +  "replace-outer-html",
      +  "replace-string",
      +  "wrap",
      +  "unwrap",
      +  "move"
      +]
    • addedInput schema / properties / items / items / properties / ops / items / properties / position
      Added value: +{
      +  "enum": [
      +    "before",
      +    "after"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / ops / items / properties / selectors
      Added value: +{
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / items / items / properties / ops / items / properties / tag
      Added value: +{
      +  "enum": [
      +    "div",
      +    "section",
      +    "footer",
      +    "header",
      +    "article",
      +    "aside"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / items / items / properties / ops / items / properties / target
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's real contribution is the atomicity guarantee ('all-or-nothing validation') and the payload ceilings (≤60KB per replace-string value/replace, ≤80KB per call). Those are non-obvious failure-mode details an agent cannot get from structured fields. It does not say whether edits land live or in a draft, which for a destructive bulk write is a notable omission.

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?

Three short clauses, no filler, and the most decision-relevant fact (bulk multi-key semantics) leads. The telegraphic style ('replace-string value/replace ≤60KB') is efficient but costs a moment of parsing.

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?

For a destructive bulk mutation over a complex 11-op nested schema with no output schema, the description covers atomicity and payload limits but omits draft-vs-live semantics, permission/auth requirements, and any hint about how the op types map to the items array. Enough to avoid obvious misuse, not enough to call it confidently.

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 75%, so the schema already documents site, context and guestToken; the description adds only the size limits attached to replace-string's value/replace fields. The deeply nested items[].ops structure with 11 op enums and many optional fields (find, target, expect, selectors, anchored) gets no explanation in either place. Baseline 3 is appropriate given the coverage level.

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+resource scoped as the multi-key form of patch_content, which cleanly separates it from the single-key sibling. 'All-or-nothing validation' adds a distinguishing behavioral trait. It stops short of a full one-line definition of what a 'key' or 'op' is, so the purpose is clear but leans on prior knowledge of patch_content.

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?

'Preferred edit path for pages over 60KB' is a concrete selection rule that tells the agent when this tool beats the alternatives, and the size ceilings further constrain applicability. It never states the inverse case explicitly (use patch_content for a single key, bulk_put_content for whole documents), so it is strong but not complete routing guidance.

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