Skip to main content
Glama

delete_slide

Remove a specific slide from a presentation by providing its unique identifier.

Instructions

Remove a slide from a presentation permanently. Use this only when you know the exact slide identifier to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYesPresentation that owns the slide.
slide_idYesSlide identifier to remove from the presentation.

Implementation Reference

  • src/index.js:273-296 (registration)
    Tool registration for "delete_slide" via server.registerTool with schema and handler. The handler delegates to callRemoteTool("delete_slide", args).
    server.registerTool(
      "delete_slide",
      {
        description:
          "Remove a slide from a presentation permanently. Use this only when you know the exact slide identifier to delete.",
        inputSchema: {
          presentation_id: z
            .string()
            .min(1)
            .describe("Presentation that owns the slide."),
          slide_id: z
            .string()
            .min(1)
            .describe("Slide identifier to remove from the presentation."),
        },
      },
      async (args) => {
        try {
          return await callRemoteTool("delete_slide", args);
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Input schema for delete_slide tool: requires presentation_id (string) and slide_id (string), both with min length 1.
    inputSchema: {
      presentation_id: z
        .string()
        .min(1)
        .describe("Presentation that owns the slide."),
      slide_id: z
        .string()
        .min(1)
        .describe("Slide identifier to remove from the presentation."),
    },
  • Handler lambda that calls callRemoteTool("delete_slide", args) to delegate the actual deletion to a remote Alai MCP endpoint.
    async (args) => {
      try {
        return await callRemoteTool("delete_slide", args);
      } catch (error) {
        return normalizeError(error);
      }
    },
  • Generic callRemoteTool helper that forwards any tool call (including delete_slide) to the remote Alai MCP server via HTTP with auth headers.
    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?

The description indicates the action is permanent ('permanently'), which is useful for a delete operation. However, it lacks details on side effects (e.g., impact on references, undo ability), and there are no annotations to supplement this. The description is adequate but not thorough for a destructive 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 consists of two short, front-loaded sentences with no unnecessary words. Every sentence adds value: first states the action, second provides usage context.

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?

For a simple delete tool with two parameters and no output schema, the description covers the essential purpose and usage condition. It could mention whether deletion is reversible, but overall it is sufficient for an agent to understand and invoke the tool correctly.

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 provides complete descriptions for both parameters (presentation_id, slide_id), achieving 100% coverage. The tool description adds no additional meaning beyond what the schema already conveys, so the baseline score of 3 is appropriate.

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 ('Remove a slide from a presentation permanently') with a specific verb and resource, and it distinguishes itself from sibling tools like create_slide and delete_presentation by focusing on slides.

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 provides explicit guidance: 'Use this only when you know the exact slide identifier to delete.' This tells the agent when to use the tool, though it doesn't mention alternatives or when not to use it.

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