Slidev MCP

List Session Slides

list_session_slides

Read-only

Look up presentations by UUID.

Returns URLs, themes, and timestamps for each requested presentation. The server does not track which presentations belong to a conversation, so pass the UUIDs you got back from render_slides. Unknown UUIDs are omitted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuids": "<uuids>"
    },
    "name": "list_session_slides"
  }
}

Input Schema

Name	Required	Description	Default
`uuids`	Yes	UUIDs of the presentations to look up (max 50), e.g. from earlier render_slides results.

Output Schema

Name	Required	Description	Default
`slides`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 25, 2026

addedInput schema / properties / uuids

Added value: +{
+  "description": "UUIDs of the presentations to look up (max 50), e.g. from earlier render_slides results.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / required
```
Added value: +[
+  "uuids"
+]
```

addedOutput schema / description

Added value: +"Presentations matching the requested UUIDs."

addedOutput schema / properties / slides / items / description
```
Added value: +"Information about a single slide deck."
```
addedOutput schema / properties / slides / items / properties / version_count
```
Added value: +{
+  "default": 0,
+  "type": "integer"
+}
```

First observedMar 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds meaningful behavior beyond annotations: it says the server does not track conversation membership and that unknown UUIDs are omitted, which affects how an agent should interpret results.

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?

The description is short and front-loaded with the core action. Each sentence adds useful information: lookup scope, return fields, the UUID source constraint, and unknown-UUID handling.

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

Completeness5/5

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

Given the simple one-parameter schema, the existing output schema, and the annotations, the description is complete enough to call the tool correctly. It covers where UUIDs come from, what happens with unknown UUIDs, and what the results contain.

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 description coverage is 100%, so the schema already documents the uuids array and the max-50 limit. The description reinforces the parameter's origin from render_slides and adds the important omission behavior for unknown UUIDs, providing value beyond the schema.

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 and resource: "Look up presentations by UUID." It also names the sibling tool that produces the UUIDs, render_slides, making the retrieval role distinct from rendering and other sibling tools.

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?

It clearly tells the agent when to use it: after render_slides, passing UUIDs returned by that tool. It also explains the key precondition that the server does not track presentation-to-conversation association. It does not explicitly compare against export_slides or screenshot_slides, but the usage context is otherwise clear.

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

All Slidev MCP tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.