Skip to main content
Glama

page_add_content

Add a content area and linked text to a Voog page, avoiding duplicates by default. Use on newly created pages to initialize content before editing.

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?

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds significant context: the GET pre-check to avoid duplicates, the default refusal on duplicate names, the force flag to bypass, and the historical issue of silent duplicates. This fully discloses the tool's behavior.

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?

The description is front-loaded with the core purpose and is reasonably concise. Each sentence adds value, covering defaults, constraints, and alternatives. Minor redundancy could be trimmed, but overall efficient.

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?

For a 5-parameter tool with no output schema, the description covers the full operation: endpoint, pre-check, defaults, valid values, force behavior, and alternative tools. It addresses edge cases and provides necessary context for correct usage.

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 description coverage is only 40% (descriptions for name and force only). The description compensates by explaining default values for name and content_type, valid content_type enum values, and the meaning of force. This adds substantial meaning beyond the 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?

The description clearly states the tool creates a content area and linked text on a page, using the POST endpoint. It distinguishes from siblings like text_update by explicitly noting that editing existing content should use that tool.

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?

The description explicitly recommends using this tool on freshly-created pages and advises using text_update for editing existing areas. It also explains the behavior with duplicate names and the force parameter, providing clear when-to-use and when-not-to-use guidance.

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