Embers: Tabletop RPG Toolkit

Update a play campaign

play_update_campaign

Idempotent

PUT updates to one campaign by id. Caller must have campaign 'contribute' permission (DM or assigned co-DM). Only supplied fields are sent; play decides how to merge. legs is NOT writable here (it is stripped): add a leg with play_add_campaign_leg, toggle one with play_set_campaign_leg_active, and change a leg's contents with the add/remove rule/item/spell/character tools. REQUIRES baseUpdatedAt: copy updatedAt from a fresh play_get_campaign read; a stale or fabricated value is rejected with OUT_OF_SYNC and nothing is written.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Mongo `_id` of the campaign.
`name`	No	Campaign name.
`image`	No	Image URL. Stored as a plain string.
`active`	No
`public`	No	Whether non-members can see the campaign.
`summary`	No	Short campaign summary. Max 150 characters.
`sessions`	No
`description`	No	Full campaign description. Markdown supported.
`hideSections`	No
`xCardEnabled`	No
`baseUpdatedAt`	Yes	REQUIRED proof that you are working from the latest version: copy the `updatedAt` value verbatim from a FRESH read of this exact record (use the matching get tool first). Values from memory, from an earlier conversation, or guessed timestamps are rejected with OUT_OF_SYNC and nothing is written. After a successful update, the response carries the new `updatedAt` — use that for any follow-up write.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 25, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```
addedInput schema / properties / active
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / baseUpdatedAt

Added value: +{
+  "description": "REQUIRED proof that you are working from the latest version: copy the `updatedAt` value verbatim from a FRESH read of this exact record (use the matching get tool first). Values from memory, from an earlier conversation, or guessed timestamps are rejected with OUT_OF_SYNC and nothing is written. After a successful update, the response carries the new `updatedAt` — use that for any follow-up write.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "Full campaign description. Markdown supported.",
+  "type": "string"
+}

addedInput schema / properties / hideSections

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "characters": {
+      "type": "boolean"
+    },
+    "logistics": {
+      "type": "boolean"
+    },
+    "players": {
+      "type": "boolean"
+    },
+    "rules": {
+      "type": "boolean"
+    },
+    "safetyTools": {
+      "type": "boolean"
+    },
+    "sessionZero": {
+      "type": "boolean"
+    },
+    "sessions": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "Mongo `_id` of the campaign.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / image

Added value: +{
+  "description": "Image URL. Stored as a plain string.",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Campaign name.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / public

Added value: +{
+  "description": "Whether non-members can see the campaign.",
+  "type": "boolean"
+}

addedInput schema / properties / sessions

Added value: +{
+  "items": {
+    "description": "Mongo `_id` reference (24-character hex string).",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / summary

Added value: +{
+  "description": "Short campaign summary. Max 150 characters.",
+  "maxLength": 150,
+  "type": "string"
+}

addedInput schema / properties / xCardEnabled
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / required

Added value: +[
+  "id",
+  "baseUpdatedAt"
+]

First observedSep 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations: it discloses the permission requirement, the partial-merge semantics ('Only supplied fields are sent; play decides how to merge'), the fact that `legs` is silently stripped, and the optimistic-concurrency failure mode (OUT_OF_SYNC, nothing written). This adds substantial context that annotations alone do not provide.

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 description is dense and well-structured, front-loading the core action before moving to permissions, merge behavior, exclusions, and concurrency. It is slightly longer than strictly necessary because it partially restates the `baseUpdatedAt` guidance already present in the schema, but every sentence carries useful information.

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?

For a mutating tool with 11 parameters and nested objects, the description covers the critical operational aspects: authorization, precondition (fresh read), merge semantics, unsupported field routing, and error behavior. The response shape is covered by the existing output schema, so that omission is acceptable.

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 64%, so the description does need to add some meaning, and it does: the partial-update contract clarifies how optional fields behave, and the `baseUpdatedAt` requirement is reinforced with a concrete workflow. However, most individual field semantics are already well described in the schema, so the description's marginal per-parameter value is moderate.

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?

The description opens with a clear verb and resource ('PUT updates to one campaign by id'), making the operation unmistakable. It further distinguishes itself from related tools by explicitly stating that `legs` is not writable here and directing to the appropriate sibling tools. This is specific enough to prevent confusion with play_update_session, play_update_page, or the leg tools.

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?

The description gives explicit when-to-use guidance: update a campaign by id, with the required permission context and a fresh `baseUpdatedAt` from play_get_campaign. It also names the alternatives for leg-related operations and clearly excludes them from this tool's scope. This is exactly the kind of routing guidance an agent needs.

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

All Embers: Tabletop RPG Toolkit 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.

Resources

Need Help?