Skip to main content
Glama

delete_image_project

Remove an image project from the Magic Hour MCP Server to manage media content and free up resources.

Instructions

Delete an image project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe image project ID to delete

Implementation Reference

  • src/index.ts:631-660 (registration)
    Complete registration of the 'delete_image_project' tool using server.tool(). Includes the schema definition (line 637 using zod) and the handler function (lines 639-658) that calls client.v1.imageProjects.delete({ id }) to delete an image project by ID. The handler includes try-catch error handling and returns success/error messages in the MCP response format.
    // ── Delete Image Project ─────────────────────────────────────────────────────
    
    server.tool(
      "delete_image_project",
      "Delete an image project.",
      {
        id: z.string().describe("The image project ID to delete"),
      },
      async ({ id }) => {
        try {
          await client.v1.imageProjects.delete({ id });
    
          return {
            content: [
              {
                type: "text" as const,
                text: `Image project ${id} deleted.`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [
              { type: "text" as const, text: `Error: ${error.message}` },
            ],
            isError: true,
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool deletes but doesn't clarify if this is permanent, reversible, requires specific permissions, or has side effects. For a destructive operation, this leaves critical behavioral traits unaddressed.

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?

The description is a single, direct sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential action, making it highly efficient and easy to parse.

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?

For a destructive tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion, potential errors, or confirmation requirements. Given the complexity and risk of deletion, more context is needed to guide safe usage.

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 schema description coverage is 100%, with the single parameter 'id' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for adequate but unenhanced coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and resource ('an image project'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'delete_video_project' or explain what distinguishes an 'image project' from other project types, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'delete_video_project' or 'get_image_project_status'. It lacks context about prerequisites, consequences, or appropriate scenarios for deletion, offering only basic functional information.

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/andrianthan/magic-hour-mcp'

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