easysociable-mcp

Get slideshow run

get_slideshow_run

Read-onlyIdempotent

Retrieve details of slideshow run by ID, including slide pages, templates, theme, revision, and review URL. Use before updating to inspect contents and capture baseRevision for concurrency locking.

Instructions

Retrieve full details of an existing Slideshow Run by runId, including complete slide pages, bound template IDs, slot contents, brand theme snapshot, current revision number, and studio review URL. Call before update_slideshow_run to inspect current slide contents and capture baseRevision for concurrency locking. Alternatives: Use list_slideshow_runs to discover runIds. Read-only query scoped to authenticated workspace owner.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`runId`	Yes	The unique Slideshow Run identifier to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description
`pages`	No	Slide pages array.
`runId`	No	Unique run identifier.
`revision`	No	Current revision number.
`studioUrl`	No	Studio review URL.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "pages": {
+      "description": "Slide pages array.",
+      "type": "array"
+    },
+    "revision": {
+      "description": "Current revision number.",
+      "type": "number"
+    },
+    "runId": {
+      "description": "Unique run identifier.",
+      "type": "string"
+    },
+    "studioUrl": {
+      "description": "Studio review URL.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.1.16Oct 5, 2026
- addedInput schema / properties / runId / description
```
Added value: +"The unique Slideshow Run identifier to retrieve."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond them: the concurrency-locking role of baseRevision and the fact that reads are scoped to the authenticated workspace owner. It stops short of describing pagination or size limits, which is a minor gap given an 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.

Conciseness5/5

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

Three sentences, zero filler: purpose first, then the sequencing requirement, then the alternative. The most actionable constraint (call before update) is front-loaded after the purpose statement.

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?

An output schema exists, so return values need not be documented, yet the description still signals what the payload contains. Combined with explicit usage sequencing and auth scoping, an agent has everything needed to call this correctly.

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% for the single runId parameter, so the schema already documents it fully. The description adds only the framing 'by runId' plus the note that list_slideshow_runs is how you obtain one, which is routing rather than parameter syntax. Baseline 3 is appropriate.

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 (Retrieve) and resource (Slideshow Run by runId) and enumerates the returned payload (slide pages, template IDs, slot contents, brand theme snapshot, revision number, review URL). This clearly distinguishes it from list_slideshow_runs, update_slideshow_run, and the template/image siblings.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('Call before update_slideshow_run to inspect current slide contents and capture baseRevision for concurrency locking') and names the alternative for discovery ('Use list_slideshow_runs to discover runIds'). Nothing about selection is left to inference.

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