Skip to main content
Glama

page_add_content

Create a content area with linked text on a fresh page. Defaults to 'body' area; set force=true to bypass duplicate name check.

Instructions

Create a content area + linked text on a page (POST /pages/{id}/contents). Use this on freshly-created pages where /contents returns [] until the admin UI's edit-mode opens the page. name must match the layout's {% content %} tag — default 'body' for unnamed, 'gallery_1' for named. content_type defaults to 'text'; valid values: text, gallery, form, content_partial, buy_button, code.

By default, the tool first GETs /pages/{id}/contents and refuses if a content area with the same name already exists — calling twice with the same name was silently creating duplicates. To edit the existing area, use text_update on its text.id. Pass force=true to skip the pre-check (legitimate use: page templates with multiple areas sharing the same name).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
page_idYes
nameNoContent area name (default 'body'; named areas match {% content name="..." %})body
content_typeNotext
forceNoSkip the duplicate-name pre-check. Default false: the tool refuses to create a second area with a name that already exists on the page. Set true only when the layout legitimately uses repeated names.
Behavior5/5

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

Discloses that the tool pre-checks for duplicate names via a GET request and refuses if duplicate exists, with a force parameter to skip. Annotations provide basic hints, but the description adds critical behavioral context beyond them.

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?

Concise and well-structured: first sentence covers purpose, then bullet-style explanations of key behaviors and options. Every sentence contributes essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, no output schema, and basic annotations, the description fully explains the tool's behavior, including the duplicate-check logic, timing context, and force flag. No missing piece.

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?

Schema coverage is 40%, but the description adds meaningful details for name (matching layout {% content %} tag, defaults), content_type (lists valid values), and force (explains duplicate check). Lacks additional info for site and page_id, but overall adds significant value.

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 explicitly states 'Create a content area + linked text on a page (POST /pages/{id}/contents)' with a specific verb and resource. It distinguishes from sibling tools like text_update by noting the alternative for editing.

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

Usage Guidelines5/5

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

Provides clear when-to-use guidance: 'Use this on freshly-created pages where /contents returns [] until the admin UI's edit-mode opens the page.' Also names an alternative: 'To edit the existing area, use text_update on its text.id.'

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/runnel/voog-mcp'

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