Skip to main content
Glama

article_add_content

Add a content area to a blog article, seeding it with text, gallery, form, or code. Defaults to a 'body' area; refuses duplicates unless force is set.

Instructions

Create a content area + linked text on a blog article (POST /articles/{id}/contents) — the article counterpart of page_add_content, with identical semantics. Use it to seed a freshly-created article's body or gallery, which /contents reports as [] until edit-mode opens the article.

name must match the article layout's {% content %} tag (default 'body'; named areas match {% content name="..." %}). content_type defaults to "text"; valid values: text, gallery, form, content_partial, buy_button, code.

Refuses by default if an area with the same name already exists, since calling twice otherwise creates duplicates. Repeated names ARE legitimate in some article layouts (observed live: two 'text-images' areas on one article) — pass force=true for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContent area name (default 'body'; named areas match {% content name="..." %})body
siteYes
forceNoSkip the duplicate-name pre-check. Default false: the tool refuses to create a second area with a name that already exists on the article.
article_idYes
content_typeNotext
Behavior5/5

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

Discloses duplicate-name refusal, the force parameter as a deliberate override for legitimate repeated areas, and the /contents [] behavior until edit-mode opens. These traits go well beyond the annotations' basic hints.

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?

Three focused paragraphs, each earning its place: main action, parameter semantics, and edge-case behavior. Front-loaded and no fluff.

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 create tool without output schema, it covers purpose, parameters, behavioral quirks, and error handling. The duplicate policy and force escape hatch are critical context that is fully explained.

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

Parameters5/5

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

Despite only 40% schema coverage, the description adds deep meaning to name (layout tag matching), content_type (valid values), and force (default false, why you'd flip it). This compensates for the sparse 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?

Clearly states it creates a content area + linked text on a blog article, and explicitly distinguishes from sibling page_add_content. The verb+resource+scope are specific and unambiguous.

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 a specific use case (seeding freshly-created article body/gallery), names the alternative tool page_add_content, and explains when to use force for duplicate names. This is explicit when/alternative 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