GoodBarber

Create event

cms_create_event

Create event. Guidance: Create one CMS agenda event from event category ids. | context: title, categories, sortDate

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>",
      "sortDate": "<sortDate>",
      "endDate": "<endDate>"
    },
    "name": "cms_create_event"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional editorial datetime in RFC 3339 format with timezone.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Optional URL slug; the server may normalize it.
`email`	No	Optional organizer contact email.
`title`	Yes	Event headline shown in feeds and on the item page.
`allDay`	No	Whether the event lasts the whole day.
`leadin`	No	Optional deck: short intro text placed at the start of the event list excerpt. Plain text: HTML tags are removed, and so is the text after a bare '<' (write 'under 12', not '<12'). Not returned by read tools, and cleared when the event is saved in the back office.
`status`	No	Publication status. Omit on create to default to published. Do not send scheduled.
`address`	No	Optional venue address for the event.
`endDate`	Yes	Event end datetime in RFC 3339 format with timezone. Must be after sortDate, or on or after it when allDay is true.
`urlShop`	No	Optional ticketing or shop URL for the event.
`latitude`	No	Optional venue latitude in decimal degrees; finite number.
`sortDate`	Yes	Event start datetime in RFC 3339 format with timezone, for example 2026-06-01T18:00:00+02:00.
`urlEvent`	No	Optional official event info URL.
`longitude`	No	Optional venue longitude in decimal degrees; finite number.
`accessTier`	No	Paywall tier. 'premium' locks the item 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 with type='agenda' to discover event category ids.
`phoneNumber`	No	Optional organizer contact phone number.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Whether end-user comments are enabled for this event.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered structurally. The description adds essentially nothing behavioral: no mention of side effects on the agenda feed, no note about duplicate handling despite non-idempotence, and no mention of the back-office interactions (e.g. leadin clearing) that the schema quietly discloses.

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 and front-loaded, but the first sentence "Create event." simply repeats the title, and the pipe-delimited "| context: ..." fragment is cryptic rather than informative. The text is tight but a portion of it does not earn its place.

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?

This is a 21-parameter, non-idempotent mutation with a nested object and no output schema, yet the description covers only three fields and gives no return information or lifecycle context. For that complexity level, the definition is far thinner than it should be.

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 all 21 parameters including the nested meta object are already documented in the schema with formats, enums, and constraints. The description's brief "context: title, categories, sortDate" list only echoes three schema-documented fields and adds no syntax or constraint detail, so the 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 states a specific verb and resource ("Create one CMS agenda event") and narrows the scope to agenda events built from category ids, which distinguishes it from the paragraph-creation siblings. It stops short of naming any specific alternative, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied through "from event category ids," which hints that category ids must be sourced first (the schema spells out cms_list_cms_sections with type='agenda'). There is no explicit when-to-use vs cms_update_event guidance, no prerequisites, and no conditions where creation should be avoided.

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.