Skip to main content
Glama

create_content

Create a new content item (page, block or global) as an unpublished draft, filled in ONE call: pass its fields in data (shapes from list_content_types {name}).

Instructions

Create a new content item (page, block or global) as an unpublished draft, filled in ONE call: pass its fields in data (shapes from list_content_types {name}). Without data you get an empty shell that stays blank until update_content/set_field fills it. A page's position decides its URL and the template that renders it, so find the right parentId with list_tree (blog posts go under their blog page); omit it only for top-level sections. Under a list page, omit type to inherit the type it lists — a mismatch is refused, since the item would never appear on that list. Returns the new item in the get_content shape (documentId, locale, revision, data…), plus a hint when it still needs filling or placing. Then publish_content. To copy an existing item instead, use duplicate_content. Requires the content.create permission (Admin, Editor, Author — an Author only within their own sections).

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": {
      "name": "<name>"
    },
    "name": "create_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoInitial field values (field name → value), same shapes as update_content. Provide this to create a FILLED draft in one call. Call list_content_types {name} 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'). list_sites reports the site's branches (`locales`). Defaults to the site default locale, which is usually English.
parentIdNodocumentId of the parent page. Required in practice for pages — find it with `list_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.7
    • changedInput schema / properties / locale / description
      Previous value: -"The 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."New value: +"The LANGUAGE BRANCH for this content — MATCH the language you are writing (Norwegian content → 'nb', English → 'en'). list_sites reports the site's branches (`locales`). Defaults to the site default locale, which is usually English."
  2. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / data / description
      Previous value: -"Initial 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."New value: +"Initial field values (field name → value), same shapes as update_content. Provide this to create a FILLED draft in one call. Call list_content_types {name} first for the field names/shapes."
    • changedInput schema / properties / parentId / description
      Previous value: -"documentId of the parent page. Required in practice for pages — find it with `tree`. Omit only for top-level pages."New value: +"documentId of the parent page. Required in practice for pages — find it with `list_tree`. Omit only for top-level pages."
  3. 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'."
  4. 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 cover only the safety hints (not read-only, not idempotent, not destructive), so the description carries the real behavioral burden and does so: the item is created as an unpublished draft, missing `data` yields an empty shell until update_content/set_field fills it, a type mismatch is refused, and the response includes a `hint` when filling/placing is still needed. It also discloses the permission model (content.create; Author limited to their own sections), which annotations do not.

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-call contract, then ordered by decision relevance (data → placement → type → return → next step → alternative → permissions). It is long and dense for a single paragraph, but nearly every clause carries decision-relevant information rather than filler.

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?

No output schema exists, yet the description states the return shape (the get_content shape: documentId, locale, revision, data) plus the conditional `hint`. Combined with the placement, type-inheritance, locale-matching and permission guidance, an agent has everything needed to invoke this 9-parameter tool correctly and interpret the result.

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 and the 3 baseline would apply on its own. The description nonetheless adds cross-parameter meaning beyond the schema: parentId determines a page's URL and rendering template, `type` is inherited under a list page and refused on mismatch, and locale is framed as the language branch that must match the content language. That is genuine added semantics over the per-field schema text.

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 precise verb and resource ('Create a new content item (page, block or global)'), including the resulting state (unpublished draft) and the one-call filling behavior. It explicitly names the alternative for copying (duplicate_content) and the follow-up (publish_content), so an agent can place it in the workflow without opening a schema.

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 concrete when-to-use rules: pass `data` to get a filled draft, call list_content_types first for shapes, use list_tree to find parentId (blog posts under their blog page), omit parentId only for top-level sections, omit `type` under a list page, and use duplicate_content to copy an existing item. Exclusions and failure conditions (type mismatch refused) are stated rather than implied.

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