EaseWeb

Get one slide

get_slide

Read-onlyIdempotent

One slide of a presentation you can see, with all of its blocks (ids and complete props).

Input Schema

Name	Required	Description	Default
`slug`	Yes	The presentation's slug (its address: /movie/<slug>/).
`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.

Output 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
`notes`	No	The speaker notes (for those who may edit; only when there are some).
`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.

Changed1 schema field changedOct 24, 2026

changedOutput schema / properties / objects / items / properties / type / description

Previous value: -"text, shape, button, line, image or code."New value: +"text, shape, button, line, image, code or table."

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / layout_warnings / items / properties / lang

Added value: +{
+  "description": "Only the text in this language has the problem.",
+  "type": "string"
+}

addedOutput schema / properties / missing_translations / items / properties / outdated

Added value: +{
+  "description": "There is a translation, written for an earlier text.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 19, 2026

addedOutput schema / properties / notes

Added value: +{
+  "description": "The speaker notes (for those who may edit; only when there are some).",
+  "type": "string"
+}

Changed4 schema fields changedOct 17, 2026

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

Changed3 schema fields changedSep 28, 2026

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds that the response contains blocks with their ids and complete props — useful return-shape context. The phrase 'a presentation you can see' hints at access scoping but is vague.

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?

A single efficient sentence with no waste, front-loading the resource and then qualifying the payload. Slightly awkward phrasing ('a presentation you can see') but structurally sound.

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 simple read tool with a full output schema, complete parameter documentation, and rich annotations, the description covers the essentials. Only the access-implied restriction ('you can see') is underspecified, which is a minor gap.

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 coverage is 100%: slug and slide_id are both fully documented in the schema, including the note that slide_id is stable while position changes on reorder. The description adds nothing beyond the schema, so 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?

States the specific resource retrieved: a single slide of a presentation, along with all of its blocks including ids and complete props. The singular framing distinguishes it implicitly from get_slides and get_presentation, though no sibling is named.

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?

No explicit when-to-use or when-to-use-instead guidance. The agent must infer from the singular 'one slide' that this is for retrieving a single known slide rather than listing (get_slides) or previewing (preview_slides). Nothing about prerequisites or alternatives is 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?