Skip to main content
Glama

EaseWeb

by host.easeweb
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoWhich presentations: "mine" (default), "shared" with you, or "open" ones of anybody.
projectNoOnly the presentations of this project (its slug), in its order; "scope" is then ignored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+  ]
+}
  3. Changed4 schema fields changed
    • 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"
+}
  4. Changed2 schema fields changed
    • 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"
+  ]
+}
  5. Changed2 schema fields changed
    • 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"
+}
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, lowering the bar. The description adds useful access semantics beyond that – notably that 'open' presentations may be read and edited by any signed-in person or agent, and that each record exposes an editability flag and access level, which helps the agent reason about permissions.

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?

Front-loaded with the scope definitions the agent needs first, then the field inventory. It is appropriately sized, though the field-list sentence reads as a run-on inventory rather than clearly separated clauses.

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?

With an output schema present, the field enumeration is partly redundant, but the access-level/editability semantics and scope meanings round out the picture. Nothing critical for a filtered, read-only list call is missing.

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%, so both parameters (scope, project) are fully documented in the schema, including the note that project overrides scope. The description largely restates the scope enum without adding syntax or precedence detail beyond what the schema already provides, so the 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 a specific verb+resource ('List presentations') and immediately defines the three scopes it can return, so an agent knows exactly what the tool yields. It doesn't explicitly contrast itself with get_presentation or the other list_* siblings, but the resource noun is distinctive enough to avoid confusion.

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?

The scope definitions tell the agent which filter to pick and which is default ('mine' default, 'shared' = granted access, 'open' = anyone can read/edit). There's no explicit 'use this instead of X' routing to get_presentation, but the when-to-use context is clear from the scope semantics.

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

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