GoodBarber

Create article

cms_create_article

Create article. Guidance: Create one CMS article from article category ids. | context: title, categories

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>",
      "categories": "<categories>"
    },
    "name": "cms_create_article"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional editorial date in RFC 3339 format, for example 2026-05-04T10:00:00+02:00.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Optional URL slug; the server may normalize it.
`title`	Yes	Headline shown in feeds and on the item page.
`author`	No	Optional byline or author display name. If omitted, the app account holder's name is used.
`leadin`	No	Optional summary: the Summary field of the back-office Info panel (also called deck). Plain text: HTML tags are removed, and so is the text after a bare '<' (write 'under 12', not '<12'). The `summary` field returned by read tools is a derived excerpt: it cannot be written and may not show this value right away, so check `leadin` instead.
`pinned`	No	Whether the article is pinned in its category listing.
`status`	No	Publication status. Omit on create to default to published. Do not send scheduled.
`accessTier`	No	Paywall tier. 'premium' locks the article behind an in-app purchase; 'free' leaves it open. Applies only to apps that sell in-app purchases.
`categories`	Yes	Non-empty category id array. Use cms_list_cms_sections to discover article category ids.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Whether end-user comments are enabled for this article.
`maxFreeParagraphs`	No	Number of body paragraphs shown as a free preview before purchase, 0 to 5. Applies only to premium in-app-purchase articles.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication.
`displaySummaryInList`	No	Whether the article summary is shown in list views. Writable only when maxFreeParagraphs is 0.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026
RemovedOct 8, 2026
First observedSep 8, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond that: it does not mention the default status of "published" when status is omitted, the deferred-publication mechanics, the paywall implications, or what happens to existing data. For a 15-parameter mutation tool, this is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the pipe-delimited "| context: title, categories" fragment reads as machine-generated filler rather than a well-structured sentence, and it spends words on the name restatement instead of the operation's real constraints. Nothing useful is front-loaded beyond the tool name.

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

Completeness2/5

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

With 15 parameters, a nested meta object, two enums, and no output schema, this is a complex tool whose description covers almost none of its substance. An agent gets no mention of the article-plus-paragraphs workflow, the status/publishedDate/publicationEndDate interactions, or the premium paywall constraints. The rich schema compensates partially, but the description itself is inadequate for the complexity.

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%, so the schema itself already explains every parameter including the enum semantics, leadin/summary distinction, and category discovery via cms_list_cms_sections. The description's "context: title, categories" only echoes the two required fields and adds no meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Create one CMS article") and its required input (article category ids), so the operation is unambiguous. It does not, however, distinguish itself from the many sibling creation tools (cms_create_article_paragraph, cms_create_event, cms_create_map), even though the singular "one CMS article" hints that the article shell is created here and paragraphs elsewhere.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "Guidance" line merely restates what is being made ("Create one CMS article from article category ids") rather than saying when to use this tool versus cms_update_article or the paragraph tools. No prerequisites, no ordering advice (e.g., create article first, then add paragraphs), and no exclusions are given.

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

All GoodBarber tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.