Skip to main content
Glama

empty_trash

Permanently delete all assets currently in the trash to free storage space. This action is destructive and irreversible.

Instructions

Permanently delete ALL assets currently in trash. DESTRUCTIVE and IRREVERSIBLE. Use this only after confirming the user wants to purge all trashed items. For deleting specific assets, use delete_assets instead. Side effect: permanently destroys all trashed assets and frees storage.

Returns: JSON with success confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'empty_trash'. Calls the Immich client to POST /trash/empty and returns a JSON success response. Decorated with @mcp.tool().
    @mcp.tool()
    async def empty_trash(ctx: Context) -> str:
        """Permanently delete ALL assets currently in trash. DESTRUCTIVE and IRREVERSIBLE.
        Use this only after confirming the user wants to purge all trashed items. For
        deleting specific assets, use delete_assets instead. Side effect: permanently
        destroys all trashed assets and frees storage.
    
        Returns: JSON with success confirmation.
        """
        await _client(ctx).empty_trash()
        return json.dumps({"success": True, "warning": "All trashed assets have been permanently deleted."})
  • Client helper method that makes the actual API call to empty the trash. Sends a POST request to the Immich '/trash/empty' endpoint.
    async def empty_trash(self) -> None:
        """Permanently empty the trash."""
        await self._request("POST", "/trash/empty")
Behavior5/5

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

Labels as 'DESTRUCTIVE and IRREVERSIBLE' and describes side effects (permanently destroys trashed assets, frees storage). No annotations were provided, so description fully covers behavioral traits.

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?

Three short sentences plus a return line, all essential. Front-loaded with purpose and warning. No wasted words.

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 tool with no parameters and an output schema exists (return value described), the description is fully sufficient. Covers purpose, usage, side effects, and result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters in input schema, so description need not explain them. It adds return value description ('Returns: JSON with success confirmation'). Baseline for 0 params is 4.

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 clearly states the verb 'permanently delete' and the resource 'ALL assets currently in trash'. It distinguishes from siblings like 'delete_assets' and 'restore_trash'.

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?

Explicitly advises to use only after user confirmation and provides an alternative tool ('delete_assets') for deleting specific items.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/drolosoft/immich-photo-manager'

If you have feedback or need assistance with the MCP directory API, please join our Discord server