Skip to main content
Glama
murphywuwu

easysociable-mcp

by murphywuwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Delete slideshow run

delete_slideshow_run
Destructive

Permanently deletes a Slideshow Run and its slide page records. Use when a run is obsolete and must be discarded; archive instead to hide it while keeping data.

Instructions

Move a Slideshow Run to trash or permanently remove it from the workspace along with its slide page records. Use only when a run is obsolete and permanently discarded. Alternatives: If you only want to hide the run from active lists while preserving review links and data, use archive_slideshow_run instead. Destructive operation requiring explicit user confirmation. Invalidates studio review URLs. Returns deletion confirmation record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesThe unique Slideshow Run identifier to permanently delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdNoDeleted run identifier.
deletedNoTrue if deletion confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "deleted": {
+      "description": "True if deletion confirmed.",
+      "type": "boolean"
+    },
+    "runId": {
+      "description": "Deleted run identifier.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changedv0.1.16
    • addedInput schema / properties / runId / description
      Added value: +"The unique Slideshow Run identifier to permanently delete."
  3. Addedv0.1.15

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond them: cascade deletion of slide page records, invalidation of studio review URLs, the requirement for explicit user confirmation, and the return value. These are concrete consequences an agent needs before invoking a destructive 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?

Five short sentences, each carrying a distinct payload (action, condition, alternative, consequences, return), with the destructive nature and the routing decision front-loaded. Nothing is padding.

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, yet the description still notes the deletion confirmation record, and it covers the destructive semantics, cascade effects, and sibling routing. Nothing an agent needs to call this safely is missing.

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% and there is a single required runId, so the schema already carries the parameter burden and the baseline is 3. The description adds no parameter-level detail; if anything, the opening phrase 'Move a Slideshow Run to trash or permanently remove it' implies a soft-vs-hard delete choice that no parameter exposes, which could mildly mislead.

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 (delete/permanently remove) and resource (Slideshow Run), plus the scope of collateral deletion (slide page records). It explicitly distinguishes itself from the sibling archive_slideshow_run, so an agent can route correctly without opening either schema.

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 an explicit when-not condition ('Use only when a run is obsolete and permanently discarded') and names the concrete alternative (archive_slideshow_run) with the exact scenario that selects it (preserving review links and data). This is about as complete as usage guidance gets.

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

Deploy Server

Other Tools