Skip to main content
Glama

bricks_instantiate_section

Instantiates a section preset, applies optional overrides and variable substitutions, and returns Bricks elements ready to add to a page.

Instructions

Create an instance of a section preset with optional overrides. Returns the Bricks elements ready to be added to a page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
overridesNoSettings overrides to apply by element key or index (e.g., { "0": { "_background": {...} } })
variablesNoVariable substitutions for {{placeholder}} values in the preset (e.g., { heading: "Hello", button_text: "Click" })
preset_nameYesName of the preset to instantiate
use_learned_stylesNoIf true, fill unfilled {{placeholders}} with learned site preferences (top colors, fonts, spacing). Explicit variables always take priority.
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It states the return behavior but does not disclose side effects, whether it modifies state, authentication needs, or rate limits. The 'returns elements' suggests a non-destructive read, but creation implies mutation – unclear.

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?

The description is two sentences, focused, and front-loaded. Every word adds value, with no redundancy or filler.

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?

No output schema exists, so the description should explain the return value sufficiently. It mentions 'Bricks elements' but lacks details on structure, error handling, or limits. Adequate but not thorough for a creation 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 description coverage is 100%, so the schema already documents all parameters. The description mentions 'optional overrides' but adds no new meaning beyond the schema. 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 clearly states the verb 'Create', resource 'section preset', and what it returns ('Bricks elements ready to be added to a page'). It is specific and distinguishes from sibling tools like bricks_create_page or bricks_create_template.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when-not-to-use, or compare with other creation tools among the siblings.

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