Skip to main content
Glama

delete_presentation

Permanently remove a presentation by providing its identifier. Use this action only when you intend to delete the deck completely.

Instructions

Delete a presentation permanently. Use this destructive action only when the caller explicitly intends to remove the deck.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYesPresentation identifier to delete permanently.

Implementation Reference

  • src/index.js:348-367 (registration)
    Registration of the 'delete_presentation' tool via server.registerTool, with input schema requiring presentation_id (string).
    server.registerTool(
      "delete_presentation",
      {
        description:
          "Delete a presentation permanently. Use this destructive action only when the caller explicitly intends to remove the deck.",
        inputSchema: {
          presentation_id: z
            .string()
            .min(1)
            .describe("Presentation identifier to delete permanently."),
        },
      },
      async (args) => {
        try {
          return await callRemoteTool("delete_presentation", args);
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Input schema definition for delete_presentation: presentation_id (z.string().min(1)) described as 'Presentation identifier to delete permanently.'
    {
      description:
        "Delete a presentation permanently. Use this destructive action only when the caller explicitly intends to remove the deck.",
      inputSchema: {
        presentation_id: z
          .string()
          .min(1)
          .describe("Presentation identifier to delete permanently."),
      },
  • Handler function that calls callRemoteTool('delete_presentation', args) to forward the request to the remote MCP endpoint.
    async (args) => {
      try {
        return await callRemoteTool("delete_presentation", args);
      } catch (error) {
        return normalizeError(error);
      }
    },
  • The callRemoteTool helper function that establishes a client connection to the remote MCP endpoint and calls the specified tool by name with provided arguments.
    async function callRemoteTool(name, args) {
      const client = new Client(
        { name: "alai-mcp-wrapper", version: "1.0.2" },
        { capabilities: {} },
      );
      const transport = new StreamableHTTPClientTransport(new URL(REMOTE_MCP_URL), {
        requestInit: {
          headers: createRemoteHeaders(),
        },
      });
    
      try {
        await client.connect(transport);
        return await client.callTool({
          name,
          arguments: args,
        });
      } finally {
        await transport.close().catch(() => {});
        await client.close().catch(() => {});
      }
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the destructive and permanent nature, but lacks details on cascading effects, permissions, or rate limits. Adequate for a simple delete action.

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 sentence that is front-loaded with the purpose and usage condition. No unnecessary words.

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

Completeness4/5

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

The tool is simple with one parameter and no output schema. The description covers purpose, usage, and a key behavioral trait (permanence). It could mention return values or error conditions but is sufficient for the tool's simplicity.

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 coverage is 100%, and the description of the sole parameter matches the schema. The description adds no extra meaning beyond what the schema already provides, meeting the baseline.

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 action (delete) and the resource (presentation), with the modifier 'permanently' that distinguishes it from non-destructive operations. Sibling tools like delete_slide operate on different resources.

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?

The description explicitly advises using this tool only when the caller intends permanent removal, providing a clear 'when to use' condition. It does not mention when not to use, but the condition covers that implicitly.

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

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