Skip to main content
Glama

bricks_patch_page

Apply partial updates to a page by sending only changed elements, reducing data transfer. Supports optimistic locking and automatically creates a backup.

Instructions

Apply partial updates to a page. Only sends changed elements instead of full page data. More efficient than bricks_update_page for small changes. Automatically creates a backup before writing (plugin-side, cannot be skipped). Supports optimistic locking via content_hash. Use content_area to patch header or footer. THEME-FIRST: when adding or restyling elements, reuse existing theme tokens and global classes (bricks_get_theme_styles / bricks_list_global_classes) instead of inline styling; prefer settings.style and _typography over _cssCustom, and the text-link/button elements over styled divs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoNew elements to add
removeNoElement IDs to remove
updateNoElements to update (must include id, only changed settings needed)
page_idYesPage ID
content_areaNoWhich content area to patch (default: content).content
content_hashNoContent hash from bricks_get_page for optimistic locking. If provided, patch fails with 409 if page was modified since read.
regenerate_cssNoWhether to regenerate CSS after patching (default: true)
Behavior4/5

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

Discloses that only changed elements are sent, automatic backup is enforced, optimistic locking causes 409 on conflict, and regenerate_css default true. No contradictions; covers main behavioral traits given no annotations.

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?

Description is multi-sentence but each sentence adds distinct value: purpose, efficiency, backup, locking, content_area, theme guidance. Not overly verbose, though theme guidance could be separate note.

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?

Covers key aspects: purpose, efficiency, backup, locking, content_area, and theme strategy. No output schema, but response is likely success/error; description doesn't specify return format but it's acceptable for a patch tool.

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 covers 100% of parameters with descriptions. Description adds minimal extra param info (theme-first guidance is for usage, not param semantics). Baseline 3 is appropriate as description does not significantly enhance schema.

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?

Description clearly states 'Apply partial updates to a page' and distinguishes from sibling bricks_update_page by noting efficiency for small changes. It specifies key features like optimistic locking and content_area support.

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?

Explicitly recommends use for small changes over bricks_update_page, mentions automatic backup, and provides theme-first guidance. Lacks explicit 'when not to use' but comparison suggests it's for incremental edits.

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/developer2013/bricks-mcp-open'

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