Skip to main content
Glama
elmapicms

elmapicms-mcp-server

Official
by elmapicms

Delete Asset

delete_asset

Remove an asset from your ElmapiCMS instance by specifying its UUID.

Instructions

Delete an asset by UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesThe asset UUID

Implementation Reference

  • The delete_asset tool handler: registers the tool with the MCP server, accepts a UUID string, and calls client.delete(`/files/${uuid}`) to perform the HTTP DELETE request.
    server.registerTool("delete_asset", {
      title: "Delete Asset",
      description: "Delete an asset by UUID",
      inputSchema: {
        uuid: z.string().describe("The asset UUID"),
      },
    }, async ({ uuid }) => {
      const result = await client.delete(`/files/${uuid}`);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    });
  • Input schema for delete_asset: requires a single 'uuid' string field describing the asset UUID.
    inputSchema: {
      uuid: z.string().describe("The asset UUID"),
    },
  • src/index.ts:39-39 (registration)
    Registration call in index.ts: registerAssetTools is called with the MCP server and client instance, which registers the delete_asset tool.
    registerAssetTools(server, client);
  • The client.delete helper method used by the tool handler to make the HTTP DELETE request to the ElmapiCMS API.
    async delete(path: string, body?: unknown): Promise<unknown> {
      const response = await fetch(`${this.baseUrl}${path}`, {
        method: "DELETE",
        headers: this.headers(),
        body: body ? JSON.stringify(body) : undefined,
      });
    
      return this.handleResponse(response);
    }
Behavior1/5

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

No annotations provided, and the description only states the basic action without disclosing important behavioral traits like irreversibility, cascading effects, or authorization requirements. This is insufficient for a destructive operation.

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 description is a single, front-loaded sentence with no wasted words. It is concise but perhaps overly minimal given the importance of clarity for a delete operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite low complexity, the description lacks critical context for a deletion tool (e.g., irreversibility, permissions, effects on related data). With no annotations, the description should provide more completeness.

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?

The input schema covers 100% of parameters with a basic description ('The asset UUID'). The tool description adds no additional meaning beyond the schema, so baseline score 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?

The description clearly states the verb (delete), resource (asset), and method (by UUID). It is unambiguous and distinguishes from sibling tools like delete_entry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, nor prerequisites or conditions for safe use. The description lacks context for appropriate usage.

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/elmapicms/elmapicms-mcp-server'

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