Agentic CMS

create_content

Create a new master content item directly without an idea, saved as draft. Ideal when content doesn't come from an idea; next step is create_variant.

Instructions

[Pipeline step 3 — Create (master)] Create a new master content item directly (without an Idea). Prefer promote_idea when the content came from an idea (keeps provenance). Status is always "draft". Next step: create_variant (step 4).

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

Input Schema

Name	Required	Description
`cta`	No	Call to action
`hook`	No	Attention-grabbing hook
`slug`	Yes	URL-friendly slug (must be unique)
`tags`	No	Content tags
`title`	Yes	Content title
`body_md`	No	Content body in Markdown
`category`	No	Content category
`media_type`	No	Type of media (video, image, etc.)
`media_urls`	No	Media URLs as key-value pairs
`core_message`	No	Core message or thesis
`fact_checked`	No	Whether content has been fact-checked
`funnel_stage`	No	Marketing funnel stage

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: status is always forced to 'draft'. However it says nothing about what happens on a duplicate slug despite declaring uniqueness, whether the operation is idempotent, or what identifier is returned for chaining to create_variant.

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 compact sentences, front-loaded with the pipeline step and the core action, followed by the exclusion and the next step. No filler or redundancy.

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

Completeness4/5

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

Covers purpose, alternative routing, forced draft status, and pipeline sequencing for a 12-parameter creation tool. The remaining gap is the return value (the new content ID needed to call create_variant) and slug-collision behavior, which matter more here since there is no output schema.

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

Parameters3/5

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

Schema description coverage is 100% across all 12 properties, so the schema already documents every parameter. The description adds no syntax, format, or constraint detail beyond what the schema fields provide, which is the baseline 3 case.

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 and resource ('Create a new master content item') and immediately scopes it ('directly, without an Idea'), which separates it from the sibling promote_idea. An agent can distinguish this from create_idea, promote_idea, and create_variant without opening any 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?

Explicitly names the alternative tool (promote_idea) and the condition that selects it (content came from an idea, keeps provenance). It also places the tool in the pipeline and names the next step (create_variant, step 4), leaving nothing to inference.

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

Deploy Server