get_slideshowRetrieve one complete slideshow by ID, returning all slides, their copy, and images so you can review or reuse the content.
One slideshow in full — its slides, their copy and their images.
| Name | Required | Description | Default |
|---|---|---|---|
| slideshowId | Yes | Slideshow id from list_slideshows. | |
| workspaceId | No | Workspace to act in. Defaults to the active one. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds genuine behavioral value by disclosing what the response contains (slides, their copy, their images) — important since no output schema exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the resource and payload contents front-loaded; there is no filler or repetition of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read tool with full schema coverage and no output schema, the description adequately covers both what it fetches and what comes back. Only minor gaps remain, such as error behavior when an id is invalid.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both slideshowId and workspaceId are already documented in the schema, including where the id comes from. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (one slideshow) and scope (in full), including the payload contents (slides, copy, images). It implicitly contrasts with the plural sibling list_slideshows via 'One slideshow', but never names an alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: the singular 'One slideshow' suggests this is the detail-fetch counterpart to list_slideshows. There is no explicit when-to-use statement, no prerequisite (e.g. obtain the id first), and no exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.