EaseWeb

Add, change or delete blocks

edit_blocks

Change some blocks of a slide and leave the others alone, in one step: "add": new blocks [{"type", "props"}] (placed on top, or at the bottom with "at_bottom": true); "update": [{"id", "props"}] -- only the given props change. The same props for several blocks at once, like selecting them in the editor: {"ids": [...], "props"}; or for a card and everything drawn on it: {"inside": <id of the card's background block>, "props"} -- that block and every block lying within its rectangle (props a block type does not have, like "link" of a code block, are skipped for it); "delete": [block ids]. Returns the slide (ids only unless "response" is "full").

Input Schema

TableJSON Schema

Name	Required	Description
`add`	No	New blocks: [{"type", "props"}].
`slug`	Yes	The presentation's slug (its address: /movie/<slug>/).
`delete`	No	Ids of blocks to delete.
`update`	No	Changes: [{"id" \| "ids": [...] \| "inside": <card block id>, "props"}].
`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.
`at_bottom`	No	Put the added blocks under the others (default: on top).
`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.

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"
+}

Changed2 schema fields changedOct 2, 2026

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"
+}

Changed2 schema fields changedSep 29, 2026

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"
+}

Changed4 schema fields changedSep 28, 2026

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

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses meaningful behavior: update only alters the given props, props a block type lacks are skipped, added blocks land on top unless at_bottom is set, and response defaults to brief. It stops short of covering permissions/auth or the semantics of the destructive 'delete' path.

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?

Front-loads the core idea in the first clause, then breaks add/update/delete into compact labeled segments. Dense and example-driven but every sentence carries operational detail; nothing is filler.

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 an 8-parameter tool with multi-shape params, the description covers the operation semantics and default behaviors well, and the output schema (present) handles return values. The main residual gap is the absence of routing guidance versus sibling edit/slide-mutation tools.

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 already 100% (baseline 3), and the description adds real meaning on top: it details the three update shapes (single id, ids list, and the 'inside' card form) and explains that 'inside' covers the card background block plus every block within its rectangle. That 'inside' semantics is not conveyed by the schema description alone.

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 states a specific verb+resource scope: 'Change some blocks of a slide and leave the others alone, in one step', and enumerates the three operations (add/update/delete) it supports. The 'blocks' focus clearly distinguishes it from siblings like edit_slides, update_slide, and replace_text without needing to open any schema.

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 implies when to use it ('leave the others alone, in one step' = a surgical partial edit) but never names an alternative tool or states a when-not condition. With siblings edit_slides, update_slide, and replace_text all in play, the agent must infer which to pick.

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?