EaseWeb

List presentations

list_presentations

Read-onlyIdempotent

Presentations: "mine" (default) -- yours; "shared" -- other people's that you were given access to; "open" -- open presentations of anybody, which every signed-in person or agent may read and edit. Each has slug, id, title, description, theme, access level, whether you can edit it, number of slides, address and its project (if any).

Input Schema

Name	Required	Description	Default
`scope`	No	Which presentations: "mine" (default), "shared" with you, or "open" ones of anybody.
`project`	No	Only the presentations of this project (its slug), in its order; "scope" is then ignored.

Output Schema

Name	Required	Description	Default
`presentations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- addedOutput schema / properties / presentations / items / properties / missing_translations / items / properties / outdated
```
Added value: +{
+  "description": "There is a translation, written for an earlier text.",
+  "type": "boolean"
+}
```

Changed3 schema fields changedOct 17, 2026

changedOutput schema / properties / presentations / items / 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 / presentations / items / properties / missing_translations_count

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

addedOutput schema / properties / presentations / items / 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"
+}

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / presentations / items / 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"
+  ]
+}

Changed4 schema fields changedSep 29, 2026

addedOutput schema / properties / presentations / items / properties / lang

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

addedOutput schema / properties / presentations / items / properties / languages

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

addedOutput schema / properties / presentations / items / 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 / presentations / items / properties / title_tr

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

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / project

Added value: +{
+  "description": "Only the presentations of this project (its slug), in its order; \"scope\" is then ignored.",
+  "type": "string"
+}

addedOutput schema / properties / presentations / items / properties / project

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

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / scope / description

Added value: +"Which presentations: \"mine\" (default), \"shared\" with you, or \"open\" ones of anybody."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "presentations": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "presentations"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The one genuine addition is the access semantics — that "open" presentations are readable and editable by anyone signed in — which is real behavioural context. The rest of the text (the field list) largely restates what the output schema already provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler sentences, but it is not front-loaded: the first token is a colon-terminated fragment rather than a statement of the action, and the line break mid-sentence makes it read like a clipped doc snippet. The most useful information (that this lists presentations filtered by scope) has to be reconstructed by the reader.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and full annotation coverage, the return shape and safety profile are already handled, so the description only needs to anchor purpose and selection rules — and it half does that. Missing are any statement of ordering/pagination and the project-overrides-scope rule, so an agent could still call it correctly but without full confidence about result ordering.

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% and the scope enum is already documented in the schema with the same wording. The description adds a minor gloss on visibility/permissions per scope but nothing about ordering, pagination, or the project-vs-scope precedence (that constraint lives only in the project parameter's schema text). Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a verb — it opens with the fragment "Presentations:" and then enumerates scope values and returned fields. The listing behaviour is inferable from the name/title and the scope enumeration, but an agent must read the whole text to conclude what the call actually does. It gives no explicit differentiation from siblings like get_presentation or list_projects.

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?

Scope semantics are spelled out well enough to imply when each variant applies (mine/shared/open), including that "open" material is editable by any signed-in person or agent. However there is no explicit routing guidance (e.g. use this to enumerate, then get_presentation for full content) and no mention of the interaction with the project parameter overriding scope, which only appears in the schema.

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?