easysociable-mcp

Archive slideshow run

archive_slideshow_run

Idempotent

Hide a completed slideshow run from default workspace lists and pickers without deleting slide data or review URLs. Reverse the change later with restore to declutter after a campaign.

Instructions

Soft-hide an active Slideshow Run from default workspace lists and pickers without deleting slide data or review URLs. Use to declutter the workspace after campaign completion. Do NOT use for permanent destruction; use delete_slideshow_run instead. Idempotent state change, fully reversible via restore_slideshow_run. Preserves all slide records, rendered assets, and external links. Returns updated SlideshowRun with status set to archived.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`runId`	No	Run identifier.
`status`	No	Updated status (archived).

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": "Updated status (archived).",
+      "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 archive."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds substantial context beyond them: soft-hide semantics, preservation of slide records, rendered assets, and external links, full reversibility via restore_slideshow_run, and the resulting status change to archived. This is rich behavioral disclosure for a mutation tool.

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 front-loaded with the core soft-hide behavior, then adds usage guidance, exclusion guidance, reversibility, preservation guarantees, and return status. Each sentence is short and contributes distinct information without restating the tool name or schema.

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 annotations, a fully covered input schema, an existing output schema, and sibling tools, the description supplies everything needed: what is hidden, what is preserved, when to use it, when not to use it, the alternative destructive sibling, reversibility, and the resulting status.

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% and the single required parameter runId is fully documented in the schema. The description adds no additional syntax, formatting, or validation detail for runId, so the baseline of 3 is appropriate when the schema carries the parameter semantics.

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+resource ('Soft-hide an active Slideshow Run') and immediately bounds it against deletion ('without deleting slide data or review URLs'). It explicitly distinguishes the operation from delete_slideshow_run, so an agent can route correctly without opening sibling schemas.

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?

It gives explicit when-to-use ('Use to declutter the workspace after campaign completion'), when-not-to-use ('Do NOT use for permanent destruction'), and the correct alternative for destruction ('use delete_slideshow_run instead'). It also names the reversal path via restore_slideshow_run.

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