easysociable-mcp

Restore slideshow run

restore_slideshow_run

Idempotent

Restore an archived or trashed carousel project to active workspace so it appears in default listings. Use it to reactivate a slideshow run after removal.

Instructions

Restore a previously archived or trashed Slideshow Run back to active workspace status, restoring it to the default projects view. Use to reactivate an archived or trashed carousel project. Alternatives: Use get_slideshow_run to inspect run contents before restoring. Idempotent state change. Returns restored SlideshowRun record visible in default workspace listings.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`runId`	No	Run identifier.
`status`	No	Restored status (active).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "runId": {
+      "description": "Run identifier.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Restored status (active).",
+      "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 restore."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description is consistent with them (the 'idempotent state change' line largely echoes the annotation). It does add genuine context beyond the structured fields: the state transition source/target and the fact that the restored record appears in default workspace listings.

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?

Short and front-loaded with the action and state transition first, and the alternative routing after. Minor redundancy: 'restoring it to the default projects view' and 'visible in default workspace listings' restate the same outcome, and the idempotence line duplicates the annotation.

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?

For a single-parameter state-change tool with an output schema, the description covers purpose, usage, alternative, and outcome adequately. Missing only edge details such as permission requirements or behavior when the run is already active, which is minor given the annotations and output schema.

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?

Only one parameter with 100% schema description coverage, so the schema already fully documents runId. The description indirectly clarifies run semantics ('archived or trashed carousel project') but adds no format, constraint, or identifier guidance beyond what the schema provides; baseline 3 applies.

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 (restore) and resource (Slideshow Run), plus the exact source states (archived or trashed) and destination (active workspace / default projects view). This clearly distinguishes it from archive_slideshow_run, delete_slideshow_run, and update_slideshow_run without opening any schema.

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?

Gives an explicit usage trigger ('Use to reactivate an archived or trashed carousel project') and names a concrete alternative (get_slideshow_run) with the condition that selects it. It stops short of stating when not to use it, e.g. that calling it on an already-active run is a no-op, so it is clear but not fully closed.

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