EaseWeb

Change title, description, theme or database

update_presentation

Change the title, description, theme or cover of a presentation you may edit, or (its author only) the setup scripts of the databases its runnable code blocks work in. The theme only sets the defaults of new slides and blocks; existing slides keep their colours. The slug (address) does not change.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	The presentation's slug (its address: /movie/<slug>/).
`theme`	No	Colour theme: the defaults of new slides and blocks.
`title`	No	New title (at most 100 characters).
`database`	No	Setup scripts of the databases the runnable code blocks work in, by language. Every viewer runs the blocks in a private database made from the script (up to 50000 characters each; an empty string removes a script). Only the author may change them; the languages left out keep their scripts.
`title_tr`	No	The title in the other languages of the site: {"en": "..."} (the languages left out keep theirs).
`cover_slide`	No	Id of the slide shown as the cover of the presentation in the lists of presentations; null: the first slide, whichever it is (the default).
`description`	No	New description; an empty string removes it.
`names_from_titles`	No	Name every slide after its title (the text block with the biggest letters, the highest one of those), in every language it is written in. From then on a slide named after its title keeps following it.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	No	The address people open in a browser.
`lang`	No	The language its texts are written in; "tr" holds the others.
`slug`	Yes	The address of the presentation: /movie/<slug>/.
`owner`	No	User name of the author.
`theme`	No
`title`	Yes
`access`	No	open, public or private.
`slides`	No	Number of slides.
`project`	No	The project it belongs to, or null.
`renamed`	No	Slides that got the name of their title.
`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.
`can_edit`	No	Whether you may change it.
`database`	No	Setup scripts of the databases of runnable code blocks (shown to the author only).
`title_tr`	No	The same text in the other languages of the site: {"en": "..."}.
`languages`	No	The languages of the site.
`cover_slide`	No	Id of the slide shown as its cover in the lists (null: an uploaded picture, or no slides).
`description`	No
`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.

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / names_from_titles

Added value: +{
+  "description": "Name every slide after its title (the text block with the biggest letters, the highest one of those), in every language it is written in. From then on a slide named after its title keeps following it.",
+  "type": "boolean"
+}

addedOutput schema / properties / renamed

Added value: +{
+  "description": "Slides that got the name of their title.",
+  "items": {
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "number": {
+        "type": "integer"
+      },
+      "slide_id": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed3 schema fields changedOct 17, 2026

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 14, 2026

addedInput schema / properties / cover_slide

Added value: +{
+  "description": "Id of the slide shown as the cover of the presentation in the lists of presentations; null: the first slide, whichever it is (the default).",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedInput schema / properties / database / properties / clickhouse

Added value: +{
+  "description": "ClickHouse SQL (statements separated by \";\") that creates and fills the database.",
+  "type": "string"
+}

addedOutput schema / properties / cover_slide

Added value: +{
+  "description": "Id of the slide shown as its cover in the lists (null: an uploaded picture, or no slides).",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / database / properties / clickhouse
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedSep 29, 2026

addedInput schema / properties / title_tr

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "The title in the other languages of the site: {\"en\": \"...\"} (the languages left out keep theirs).",
+  "type": "object"
+}

addedOutput schema / properties / lang

Added value: +{
+  "description": "The language its texts are written in; \"tr\" holds the others.",
+  "type": "string"
+}

addedOutput schema / properties / languages

Added value: +{
+  "description": "The languages of the site.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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 / title_tr

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

Changed1 schema field changedSep 29, 2026

addedOutput schema / properties / project

Added value: +{
+  "description": "The project it belongs to, or null.",
+  "properties": {
+    "slug": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedSep 28, 2026
- addedInput schema / properties / title / maxLength
```
Added value: +100
```

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / database

Added value: +{
+  "additionalProperties": false,
+  "description": "Setup scripts of the databases the runnable code blocks work in, by language. Every viewer runs the blocks in a private database made from the script (up to 50000 characters each; an empty string removes a script). Only the author may change them; the languages left out keep their scripts.",
+  "properties": {
+    "mongodb": {
+      "description": "MongoDB shell (mongosh JavaScript) that creates and fills the database.",
+      "type": "string"
+    },
+    "redis": {
+      "description": "Redis commands that creates and fills the database.",
+      "type": "string"
+    },
+    "sql": {
+      "description": "PostgreSQL SQL that creates and fills the database.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / database

Added value: +{
+  "description": "Setup scripts of the databases of runnable code blocks (shown to the author only).",
+  "properties": {
+    "mongodb": {
+      "type": "string"
+    },
+    "redis": {
+      "type": "string"
+    },
+    "sql": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedSep 28, 2026

addedInput schema / properties / description / description

Added value: +"New description; an empty string removes it."

addedInput schema / properties / theme / description

Added value: +"Colour theme: the defaults of new slides and blocks."

addedInput schema / properties / title / description

Added value: +"New title (at most 100 characters)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "access": {
+      "description": "open, public or private.",
+      "type": "string"
+    },
+    "can_edit": {
+      "description": "Whether you may change it.",
+      "type": "boolean"
+    },
+    "description": {
+      "type": "string"
+    },
+    "id": {
+      "type": "integer"
+    },
+    "owner": {
+      "description": "User name of the author.",
+      "type": "string"
+    },
+    "slides": {
+      "description": "Number of slides.",
+      "type": "integer"
+    },
+    "slug": {
+      "description": "The address of the presentation: /movie/<slug>/.",
+      "type": "string"
+    },
+    "theme": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "description": "The address people open in a browser.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "slug",
+    "title"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing non-obvious semantics: the theme only affects new slides/blocks and not existing ones, the slug never changes, omitted languages keep their scripts, and an empty string removes a script. It also surfaces the permission model (author-only for database scripts, edit rights otherwise).

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?

Three tight sentences, front-loaded with the full set of changeable fields, followed only by two genuinely informative clarifications about theme scope and slug immutability. No filler or repetition.

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 mutation tool with nested objects, an output schema, and 100% schema coverage, the description covers the important behaviors and constraints. It omits mention of title_tr and names_from_titles, but those are fully documented in the schema, so the gap is minor.

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% and the schema already explains each field in depth (theme defaults, per-language database scripts, empty-string removal, cover_slide null meaning). The description's theme and slug notes largely restate what the schema says, so it adds little parameter-level meaning beyond the baseline.

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?

States a specific verb (change) plus the exact resources it mutates: title, description, theme, cover, and database setup scripts of a presentation. This clearly separates it from update_slide, edit_slides, edit_blocks, and update_project without the agent needing to open schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real precondition — the presentation must be one 'you may edit', and the database scripts are changeable by 'its author only' — which tells the agent when the call will succeed. It does not, however, name alternatives or say when not to use this tool (e.g. versus name_slides_after_titles, which overlaps the names_from_titles parameter).

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?