Skip to main content
Glama
tanker327

Prompts MCP Server

by tanker327

delete_prompt

Remove a prompt template by name from the Prompts MCP Server to manage prompt storage and organization.

Instructions

Delete a prompt by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the prompt to delete

Implementation Reference

  • The primary handler for the 'delete_prompt' MCP tool. Validates the 'name' argument, calls fileOps.deletePrompt, and returns a success message.
    private async handleDeletePrompt(args: ToolArguments): Promise<CallToolResult> {
      if (!args.name) {
        throw new Error('Name is required for delete_prompt');
      }
      
      await this.fileOps.deletePrompt(args.name);
      return {
        content: [
          {
            type: 'text',
            text: `Prompt "${args.name}" deleted successfully`,
          } as TextContent,
        ],
      };
    }
  • Core helper function that performs the actual file deletion by constructing the filepath and using fs.unlink.
    async deletePrompt(name: string): Promise<boolean> {
      const fileName = this.sanitizeFileName(name) + '.md';
      const filePath = path.join(this.promptsDir, fileName);
      try {
        await fs.unlink(filePath);
        return true;
      } catch (error) {
        throw new Error(`Prompt "${name}" not found`);
      }
    }
  • Input schema definition for the 'delete_prompt' tool, specifying the required 'name' string parameter.
    {
      name: 'delete_prompt',
      description: 'Delete a prompt by name',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the prompt to delete',
          },
        },
        required: ['name'],
      },
    },
  • src/tools.ts:144-145 (registration)
    Registration in the handleToolCall switch statement that routes 'delete_prompt' calls to the handler.
    case 'delete_prompt':
      return await this.handleDeletePrompt(toolArgs);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool deletes a prompt, implying a destructive mutation, but doesn't cover critical aspects like permissions needed, whether deletion is permanent or reversible, error handling (e.g., if the prompt doesn't exist), or side effects. This leaves significant gaps for a mutation tool.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permanence, permissions), error scenarios, or what happens post-deletion. Given the complexity of deletion operations and the absence of structured data to compensate, more context is needed to be fully helpful.

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 parameter 'name' fully documented in the schema as 'Name of the prompt to delete'. The description adds no additional meaning beyond this, such as format constraints or examples. Given the high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Delete a prompt by name' clearly states the action (delete) and resource (prompt) with a specific method (by name). It distinguishes from siblings like 'get_prompt' or 'list_prompts' by indicating a destructive operation, though it doesn't explicitly contrast with all siblings like 'add_prompt' or 'create_structured_prompt'. This makes it clear but not fully differentiated.

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. It doesn't mention prerequisites (e.g., needing an existing prompt), exclusions (e.g., not for structured prompts), or direct comparisons to siblings like 'add_prompt' or 'get_prompt'. Without such context, users must infer usage from the name alone.

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

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