Skip to main content
Glama

get_presentations

Retrieve a list of your presentations to select one for editing, exporting, or deleting.

Instructions

List presentations owned by the authenticated user. Use this when you need to pick an existing presentation_id before editing, exporting, or deleting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.js:216-230 (registration)
    Registration of the 'get_presentations' tool with the MCP server. The handler calls 'callRemoteTool' which forwards the request to the remote Alai MCP endpoint. No input schema is required (empty object).
    server.registerTool(
      "get_presentations",
      {
        description:
          "List presentations owned by the authenticated user. Use this when you need to pick an existing presentation_id before editing, exporting, or deleting.",
        inputSchema: {},
      },
      async () => {
        try {
          return await callRemoteTool("get_presentations", {});
        } catch (error) {
          return normalizeError(error);
        }
      },
    );
  • Handler function for get_presentations. Delegates to 'callRemoteTool' which creates an MCP client and proxies the call to the remote Alai service.
    async () => {
      try {
        return await callRemoteTool("get_presentations", {});
      } catch (error) {
        return normalizeError(error);
      }
    },
  • Helper function that forwards tool calls to the remote Alai MCP endpoint using a streaming HTTP client transport.
    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(() => {});
      }
    }
  • Helper function that normalizes errors from the remote tool call into a structured error response with optional auth guidance.
    function normalizeError(error) {
      const message =
        error instanceof Error ? error.message : "Unknown upstream error";
    
      return {
        content: [
          {
            type: "text",
            text: `Alai upstream request failed: ${message}`,
          },
          ...(authGuidance()
            ? [
                {
                  type: "text",
                  text: authGuidance(),
                },
              ]
            : []),
        ],
        isError: true,
      };
    }
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It states the tool lists presentations 'owned by the authenticated user,' implying read-only access. However, it does not mention whether results are paginated, sorted, or limited, nor does it specify the output format. This is adequate for a simple list operation but leaves some gaps.

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 extremely concise: two sentences. The first states the action and scope, the second provides usage guidance. Every word adds value, and it is front-loaded with the core purpose.

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?

Given no output schema and zero parameters, the description covers the tool's purpose and usage context well. It does not describe the return format or fields, which might be helpful, but the omission is minor for a listing tool that simply returns presentation objects. Sibling tools like 'get_themes' are similarly brief.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so no parameter documentation is needed. The description does not add parameter-level details, but none are required. With 100% schema coverage (no params), the baseline is 4.

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 that the tool lists presentations owned by the authenticated user, using a specific verb ('List') and resource ('presentations'). It distinguishes itself from sibling tools like 'create_slide' and 'delete_presentation' by explicitly mentioning its role as a prerequisite for editing, exporting, or deleting.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool: 'when you need to pick an existing presentation_id before editing, exporting, or deleting.' This provides clear context and alternative actions (the editing/exporting/deleting tools), helping the agent decide correctly.

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