EaseWeb

Change a slide

update_slide

Change a slide: its name, size, background colour / picture, entrance transition, and -- when "objects" is given -- its COMPLETE list of blocks: blocks with an existing "id" are kept (their props are merged with the given ones), blocks without an id are added, blocks not in the list are deleted. Returns the slide (ids only unless "response" is "full").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`h`	No	Canvas height in px (default 720).
`w`	No	Canvas width in px (200-4000, default 1280).
`bg`	No	Background colour, #rrggbb.
`fit`	No	How the background picture fits.
`name`	No	Slide name (at most 100 characters), in the language of the presentation.
`slug`	Yes	The presentation's slug (its address: /movie/<slug>/).
`name_tr`	No	The slide name in the other languages of the site: {"en": "..."}.
`objects`	No	Blocks of the slide, bottom to top: [{"type": "text"\|"shape"\|"button"\|"line"\|"image"\|"code", "props": {...}}]. Missing props take the presentation theme's defaults (every prop is described in the block format reference). A link to a slide of the same presentation may be given as {"kind": "slide", "slide_number": N}.
`response`	No	"brief" (default): only the ids, numbers and types of the slides and blocks; "full": every prop of every block too.
`slide_id`	Yes	The id of a slide (stable, the "id" of the slide in the presentation). Its number (position) changes when slides are reordered.
`background`	No	Background picture: the "src" of an uploaded picture; null removes it.
`transition`	No	Entrance effect of this incoming slide (default: none).	none
`base_version`	No	Optional: the "version" of the slide as you read it. The change is refused (409 conflict) when somebody changed the slide meanwhile, instead of overwriting their work.
`transition_duration`	No	Animation duration in milliseconds (100-3000, default 500); not auto advance. Values outside the range are clamped.

Output Schema

TableJSON Schema

Name	Required	Description
`h`	No
`w`	No
`bg`	No
`id`	Yes	Stable id of the slide.
`fit`	No
`url`	No	The address people open in a browser.
`name`	No
`number`	Yes	1-based position; changes when slides are reordered.
`name_tr`	No	The same text in the other languages of the site: {"en": "..."}.
`objects`	Yes	Blocks, bottom to top ("props" only in the full form).
`version`	No	Stamp of the content as it is now: give it back as "base_version" to change it only if nobody else did meanwhile.
`background`	No	The "src" of the background picture, or null.
`transition`	No	Entrance effect of this incoming slide.
`layout_warnings`	No	How the changed slides will probably look: texts too long for their blocks, blocks outside the slide, texts over each other (estimated -- look at them).
`transition_duration`	No	Animation milliseconds, not auto advance.
`missing_translations`	No	What is not translated yet into the other languages of the site (add it): the first ones; "missing_translations_count" says how many there are.
`missing_translations_count`	No	How many texts are not translated yet.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / base_version

Added value: +{
+  "description": "Optional: the \"version\" of the slide as you read it. The change is refused (409 conflict) when somebody changed the slide meanwhile, instead of overwriting their work.",
+  "type": "string"
+}

addedOutput schema / properties / layout_warnings

Added value: +{
+  "description": "How the changed slides will probably look: texts too long for their blocks, blocks outside the slide, texts over each other (estimated -- look at them).",
+  "items": {
+    "properties": {
+      "block_id": {
+        "type": "integer"
+      },
+      "detail": {
+        "type": "string"
+      },
+      "problem": {
+        "description": "overflow, cut, outside or overlap.",
+        "type": "string"
+      },
+      "slide_id": {
+        "type": "integer"
+      },
+      "slide_number": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / missing_translations / description

Previous value: -"What is not translated yet into the other languages of the site (add it)."New value: +"What is not translated yet into the other languages of the site (add it): the first ones; \"missing_translations_count\" says how many there are."

addedOutput schema / properties / missing_translations_count

Added value: +{
+  "description": "How many texts are not translated yet.",
+  "type": "integer"
+}

addedOutput schema / properties / version

Added value: +{
+  "description": "Stamp of the content as it is now: give it back as \"base_version\" to change it only if nobody else did meanwhile.",
+  "type": "string"
+}

Changed4 schema fields changedOct 2, 2026

addedInput schema / properties / transition

Added value: +{
+  "default": "none",
+  "description": "Entrance effect of this incoming slide (default: none).",
+  "enum": [
+    "none",
+    "fade",
+    "slide-left",
+    "slide-right",
+    "zoom"
+  ],
+  "type": "string"
+}

addedInput schema / properties / transition_duration

Added value: +{
+  "default": 500,
+  "description": "Animation duration in milliseconds (100-3000, default 500); not auto advance. Values outside the range are clamped.",
+  "type": "integer"
+}

addedOutput schema / properties / transition

Added value: +{
+  "description": "Entrance effect of this incoming slide.",
+  "enum": [
+    "none",
+    "fade",
+    "slide-left",
+    "slide-right",
+    "zoom"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / transition_duration

Added value: +{
+  "description": "Animation milliseconds, not auto advance.",
+  "maximum": 3000,
+  "minimum": 100,
+  "type": "integer"
+}

Changed4 schema fields changedSep 29, 2026

changedInput schema / properties / name / description

Previous value: -"Slide name (at most 100 characters)."New value: +"Slide name (at most 100 characters), in the language of the presentation."

addedInput schema / properties / name_tr

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "The slide name in the other languages of the site: {\"en\": \"...\"}.",
+  "type": "object"
+}

addedOutput schema / properties / missing_translations

Added value: +{
+  "description": "What is not translated yet into the other languages of the site (add it).",
+  "items": {
+    "properties": {
+      "block_id": {
+        "type": "integer"
+      },
+      "lang": {
+        "type": "string"
+      },
+      "slide_id": {
+        "type": "integer"
+      },
+      "slide_number": {
+        "type": "integer"
+      },
+      "what": {
+        "description": "title, slide name or block.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / name_tr

Added value: +{
+  "description": "The same text in the other languages of the site: {\"en\": \"...\"}.",
+  "type": "object"
+}

Changed6 schema fields changedSep 28, 2026

changedInput schema / properties / name / description

Previous value: -"Slide name (at most 30 characters)."New value: +"Slide name (at most 100 characters)."

addedInput schema / properties / name / maxLength
```
Added value: +100
```

addedInput schema / properties / response

Added value: +{
+  "description": "\"brief\" (default): only the ids, numbers and types of the slides and blocks; \"full\": every prop of every block too.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / description

Added value: +"A slide; the brief form (the default of the tools that change slides) has only id, number, name, url and the id and type of every block."

changedOutput schema / properties / objects / description

Previous value: -"Blocks, bottom to top."New value: +"Blocks, bottom to top (\"props\" only in the full form)."

changedOutput schema / properties / objects / items / required

Previous value: -[
-  "id",
-  "type",
-  "props"
-]New value: +[
+  "id",
+  "type"
+]

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "background": {
+      "description": "The \"src\" of the background picture, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bg": {
+      "type": "string"
+    },
+    "fit": {
+      "type": "string"
+    },
+    "h": {
+      "type": "integer"
+    },
+    "id": {
+      "description": "Stable id of the slide.",
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "number": {
+      "description": "1-based position; changes when slides are reordered.",
+      "type": "integer"
+    },
+    "objects": {
+      "description": "Blocks, bottom to top.",
+      "items": {
+        "properties": {
+          "id": {
+            "type": "integer"
+          },
+          "props": {
+            "description": "Every prop of the block (see the block format reference).",
+            "type": "object"
+          },
+          "type": {
+            "description": "text, shape, button, line, image or code.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "type",
+          "props"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "The address people open in a browser.",
+      "type": "string"
+    },
+    "w": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "number",
+    "objects"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

The description is genuinely informative: it discloses that omitted blocks are deleted and that id-bearing blocks are merged, which is exactly the kind of risk context that matters. However, it explicitly declares deletion of existing blocks while the annotations set destructiveHint=false, which per the MCP spec means 'only additive updates'. That is a direct inconsistency between the documented behavior and the structured safety hint, so the highest transparency marks cannot be given.

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?

Two sentences, front-loaded with the verb and the affected surface, then the one non-obvious rule (objects replacement) emphasized in caps. The em-dash aside is dense but every clause removes a genuine ambiguity; nothing is padding.

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?

For a 14-parameter mutation tool with nested objects and an output schema, the description covers the riskiest gaps (block replacement semantics, response verbosity) while correctly leaving scalar parameters to the exhaustive schema. It does not note the absence of an undo path or permission requirements, which keeps it short of a 5.

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 description coverage is 100%, so the baseline is 3, and the description earns above that by adding semantics the schema does not carry: the id-based merge, add, and delete rules for objects and the brief/full response switch. It adds real meaning on the one parameter (objects) whose behavior is most easily misused.

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 (change) and resource (a slide) and then enumerates the exact attributes under its control: name, size, background colour/picture, entrance transition, and the full block list. It is clear and scoped, but it never names a sibling (e.g. edit_blocks, edit_slides, update_presentation), so the agent gets no explicit routing help for the overlapping update tools.

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?

It explains one important usage condition -- that the objects parameter triggers whole-list replacement -- and hints at the response mode, but it never states when to prefer this tool over edit_blocks/edit_slides or what prerequisites exist. Usage is implied rather than stated.

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

All EaseWeb 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?