Skip to main content
Glama

create_content

Create a new page, block, or global as a draft in Paperboy CMS, optionally under a parent. Pass field data in one call to fill it, or omit data for an empty shell.

Instructions

Create a new content item (page/block/global) as a draft. Pass the field content in data (field name → value, same shapes as update_content) to fill the page in ONE call — strongly preferred for a one-shot create. If you omit data it creates an EMPTY shell (name + auto slug only) that you MUST then fill with update_content/set_field, or the page stays blank. Either way: get_content_type first to learn the field names/shapes for this type. IMPORTANT: pages almost always belong UNDER an existing parent — a page's position decides its URL and which template the frontend renders it with (a blog post created at root gets a generic layout and looks empty when published). Call tree first and pass the right parentId (e.g. blog posts/articles go under their blog/list page). Omit parentId ONLY for genuinely top-level pages like the site's main sections. Under a LIST PAGE, the type must match what that page lists (its listedType): OMIT type to inherit it, or a mismatch is refused (the content would publish but never appear on the list).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoInitial field values (field name → value), same shapes as update_content. Provide this to create a FILLED draft in one call. Call get_content_type first for the field names/shapes.
nameYesDisplay name of the item (also the source of a page's auto slug), e.g. 'Summer sale 2026'.
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
slugNoURL slug for a page. Omit to auto-derive from the name.
typeNoContent type name. Under a list-page parent, OMIT to inherit the type that page lists; a mismatch is refused unless allowTypeMismatch.
localeNoThe LANGUAGE BRANCH for this content — MATCH the language you are writing (Norwegian content → 'nb', English → 'en'). Call list_locales to see the site's branches. Defaults to the site default locale, which is usually English.
parentIdNodocumentId of the parent page. Required in practice for pages — find it with `tree`. Omit only for top-level pages.
allowTypeMismatchNoSet true ONLY for a deliberate sub-page whose type differs from the parent list page's listedType
allowLanguageMismatchNoSet true ONLY to deliberately create text whose language differs from the locale branch (the guard otherwise refuses, so e.g. Norwegian text can't silently land on the 'en' branch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / name / description
      Added value: +"Display name of the item (also the source of a page's auto slug), e.g. 'Summer sale 2026'."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (mutation, non-destructive, non-idempotent). The description adds real behavioral consequences beyond them: omitting data leaves a blank page, a root-level blog post renders with a generic/empty layout, and type/language mismatches are refused ('a mismatch is refused'). These are refusal and side-effect disclosures that annotations do not carry.

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?

Front-loaded with the core action and the one-shot `data` guidance before the caveats. It is dense and long for a single paragraph with heavy ALL-CAPS emphasis, but the length is largely justified by the number of non-obvious constraints. Loses a point for the wall-of-text presentation.

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 9-parameter mutation tool with no output schema, the description covers prerequisites (get_content_type, tree), guard behavior, the empty-vs-filled create fork, and top-level vs nested placement. Nothing an agent needs to call it correctly is missing; output values are not needed here.

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 100%, so the schema already documents each parameter; baseline 3. The description nonetheless adds meaning beyond the schema by explaining cross-parameter relationships (parentId determines URL and frontend template; type inheritance under a list page; allowTypeMismatch as a deliberate override), which the per-parameter schema text does not connect.

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?

States a specific verb+resource+scope: 'Create a new content item (page/block/global) as a draft.' It explicitly positions itself against siblings (update_content, set_field, get_content_type, tree) so an agent can tell it apart without opening schemas.

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?

Gives explicit when/when-not: pass `data` for a one-shot filled create (strongly preferred), omit it to get an empty shell that must be filled later; call get_content_type first; call tree first and set parentId; omit parentId only for genuinely top-level pages. Alternatives and preconditions are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.