easysociable-mcp

Archive image

archive_image

Idempotent

Hide an image from active media pickers without deleting its file. Use to declutter retired assets; reversible via restore, while existing slides keep rendering.

Instructions

Archive an image asset to soft-hide it from active media pickers without deleting binary files from storage. Call to declutter media library when an image is retired from active use. For permanent deletion, use delete_image instead. Idempotent state transition, fully reversible via restore_image. Slides and carousels currently referencing this image continue to display and render without disruption. Returns updated Image record with status set to archived.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`imageId`	Yes	The unique image asset identifier to archive.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No	Updated status (archived).
`imageId`	No	Image asset ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "imageId": {
+      "description": "Image asset ID.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Updated status (archived).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.1.16Oct 5, 2026
- addedInput schema / properties / imageId / description
```
Added value: +"The unique image asset identifier to archive."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare non-destructive, idempotent, non-readOnly, but the description adds substantial context beyond them: binaries are retained in storage, the change is fully reversible via restore_image, and referencing slides/carousels keep rendering uninterrupted. That dependency-impact disclosure is exactly what an agent needs before mutating shared content.

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?

Front-loads the core action and its key constraint, then adds alternatives and side effects in descending priority. It runs slightly long at five sentences, and the return-value sentence is partly redundant with the output schema, but no sentence is filler.

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?

For a single-param state-transition tool with an output schema present, the description covers action, scope, reversibility, side effects on dependents, and the deletion alternative. An agent has everything needed to call it correctly and anticipate consequences.

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 the single parameter (imageId) is fully documented in the schema, so the description adds nothing parameter-specific. Baseline 3 applies when the schema does the heavy lifting.

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+resource ('Archive an image asset') and immediately scopes it against the binary-preserving behavior ('soft-hide it from active media pickers without deleting binary files'). It explicitly names the sibling tools delete_image and restore_image, so an agent can route correctly without reading other 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?

Gives the triggering condition ('Call to declutter media library when an image is retired from active use') and an explicit alternative with its own condition ('For permanent deletion, use delete_image instead'). This is textbook when-to-use / when-not-to-use guidance.

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