easysociable-mcp

Restore image

restore_image

Idempotent

Reactivates an archived or trashed image asset in the workspace media library, making it selectable again in slide slot editors.

Instructions

Restore a previously archived or trashed image asset back to active status in the workspace media library. Call to unhide a retired asset and make it selectable again in slide slot editors. Alternatives: Use get_image to inspect asset details before restoring. Idempotent state transition. Returns restored Image record visible in default media queries.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No	Restored status (active).
`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": "Restored status (active).",
+      "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 restore."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds value by naming the two source states it reverses (archived or trashed) and the downstream effect on slide slot editors, though 'Idempotent state transition' largely restates the idempotentHint annotation.

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?

The core action and effect are front-loaded in the first two sentences. The trailing 'Returns restored Image record visible in default media queries' is somewhat redundant given an output schema exists, costing a bit of efficiency.

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-parameter, idempotent state-transition tool with rich annotations and an output schema, the description covers the action, the states involved, the user-visible effect, and a related tool. Nothing an agent needs to invoke it correctly 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 description coverage is 100% and the single imageId parameter is fully documented in the schema. The description adds no syntax, format, or lookup guidance beyond what the schema already says, so the 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), resource (image asset), and the exact state transition (archived/trashed back to active), which cleanly separates it from archive_image and delete_image in the sibling list.

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 clear context for when to call it ('unhide a retired asset', 'make it selectable again in slide slot editors') and points to get_image for pre-inspection. It does not state when NOT to use it, e.g. that delete_image is permanent and unrecoverable by this tool, which is the key exclusion an agent would need.

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