Skip to main content
Glama

Add Block

add_block

Add a new content block to a page. Available types: hero, features, testimonials, faq, gallery, stats, cta, contact, split, process, serviceselector, pricing, video, logobar, numberedfeatures, map, menu, richtext. If content is omitted, sensible defaults are generated.

Annotations: read-only=false, destructive=false, idempotent=false, open-world=false. Why: Adds a new section to a page; nothing existing is overwritten (additive, not destructive). Not idempotent: each call adds another section. Closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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_id": "<site_id>",
      "page_slug": "<page_slug>",
      "block_type": "<block_type>"
    },
    "name": "add_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoBlock content. If omitted, defaults are used.
site_idYes
variantNoLayout variant. If omitted, a sensible default is chosen.
positionNo"start", "end" (default), or "after:block-N"
page_slugYes
block_typeYesBlock type (see list_block_types)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly=false, destructive=false, idempotent=false and include a rationale explaining additive, non-idempotent, closed-world behavior plus the publish_site gating. The description contributes the additional behavioral fact that content may be omitted and defaults will be synthesized, which is not visible in the annotations. It does not, however, say what the call returns or how the new block is identified afterward.

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?

Two sentences with the action front-loaded and the type list placed where it is needed; nothing is padded. The enumeration is long but functional, since it is the only place the valid types are spelled out.

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?

For a six-parameter mutation with a nested content object and no output schema, the description covers purpose, type domain, and defaulting behavior adequately. The remaining gap is the return value and the block-identifier convention implied by position's "after:block-N", which the agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 67% schema coverage, the description meaningfully compensates by enumerating the concrete block_type values, which the schema leaves as a bare string with only a pointer to list_block_types and no enum. It also restates the content-defaults behavior, though it adds nothing for page_slug or site_id, which have no schema descriptions.

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?

The description opens with a specific verb and resource ("Add a new content block to a page") and enumerates the 18 valid block types, so the scope is unambiguous. It does not explicitly contrast itself with the sibling update_block/remove_block, leaving that distinction to be inferred from the verb alone.

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

Usage Guidelines3/5

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

Usage is implied by the verb and by "If content is omitted, sensible defaults are generated," which tells the agent it can call with minimal input. There is no explicit statement of when to prefer add_block over update_block, nor any prerequisite (e.g., that page_slug must already exist) or pointer to the sibling list_block_types other than the schema's own reference.

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.