GoodBarber

Update event

cms_update_event

DestructiveIdempotent

Update event. Guidance: Update one CMS agenda event by event id. | context: id

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

Input Schema

Name	Required	Description
`id`	Yes	Event id returned by cms_list_events.
`date`	No	Omit to keep the current editorial datetime; send an RFC 3339 datetime with timezone to replace it.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Omit to keep the current slug; send to replace it.
`email`	No	Omit to keep the current organizer email; send to replace it.
`title`	No	Omit to keep the current headline; send to replace it.
`allDay`	No	Omit to keep the current all-day flag; send true or false to replace it.
`leadin`	No	Omit to keep the current deck; send to replace it. 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	Omit to keep the current publication state. Do not send scheduled.
`address`	No	Omit to keep the current venue address; send to replace it.
`endDate`	No	Omit to keep the current event end; send an RFC 3339 datetime with timezone to replace it.
`urlShop`	No	Omit to keep the current ticketing or shop URL; send to replace it.
`latitude`	No	Omit to keep the current venue latitude; send a finite number to replace it.
`sortDate`	No	Omit to keep the current event start; send an RFC 3339 datetime with timezone to replace it.
`urlEvent`	No	Omit to keep the current official event info URL; send to replace it.
`longitude`	No	Omit to keep the current venue longitude; send a finite number to replace it.
`accessTier`	No	Replacement 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`	No	Omit to keep placement. Send non-empty category ids to replace placement.
`phoneNumber`	No	Omit to keep the current organizer phone number; send to replace it.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Omit to keep the current comments setting; send true or false to replace it.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication. Send an empty string to clear an existing scheduled unpublication.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare that this is a destructive, idempotent, open-world write operation. The description adds almost no behavioral context beyond identifying the resource and id, such as partial-update semantics or what happens to omitted fields.

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?

The definition is very short and front-loads the action. It contains some redundancy in 'Update event' versus the title, but it avoids unnecessary wording.

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

Completeness3/5

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

The expanded schema and annotations carry most of the needed detail for this 22-parameter mutation tool. However, the description itself is sparse for such a complex operation and does not mention partial update behavior or alternatives.

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 detailed parameter semantics are already carried by the schema. The description only mentions the id parameter and adds no meaningful interpretation beyond that baseline.

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: update one CMS agenda event by event id. It is clear what the tool does, though it does not explicitly distinguish itself from paragraph-specific or create/delete/get siblings.

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 description implies usage by saying it updates one event by id, but gives no guidance on when to use it versus alternatives such as cms_update_event_paragraph or cms_create_event. There are no exclusions or prerequisites stated in the description itself.

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.