Skip to main content
Glama

tosea_export_presentation

Export completed presentations to PDF, PPTX, or image-based PPTX formats for sharing and distribution.

Instructions

Queue an export job for a completed presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYes
output_formatYes
idempotency_keyNo

Implementation Reference

  • The tool 'tosea_export_presentation' is defined and registered in src/tools.ts. It validates inputs via Zod and calls client.exportPresentation to handle the logic.
    server.tool(
      "tosea_export_presentation",
      "Queue an export job for a completed presentation.",
      {
        presentation_id: z.string().uuid(),
        output_format: z.enum(["pdf", "pptx", "pptx_image"]),
        idempotency_key: z.string().min(8).optional()
      },
      async ({ presentation_id, output_format, idempotency_key }) => {
        try {
          return asToolResult(
            await client.exportPresentation({
              presentationId: presentation_id,
              outputFormat: output_format,
              idempotencyKey: idempotency_key
            })
          );
        } catch (error) {
          throw wrapToolError(error);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool queues an export job, implying an asynchronous or background process, but lacks details on job status, polling, error handling, or rate limits. The mention of 'completed presentation' hints at a prerequisite, but more behavioral context is needed for effective use.

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 that front-loads the core action ('Queue an export job') without unnecessary words. It's appropriately sized for the tool's complexity, with zero waste or redundancy.

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?

Given the tool's complexity (3 parameters, no annotations, no output schema), the description is incomplete. It lacks details on job queuing behavior, output handling, error cases, and parameter semantics. Without annotations or output schema, the description should provide more context to guide an agent effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It adds no information about the three parameters (presentation_id, output_format, idempotency_key), such as their roles or constraints. The description mentions 'export job' and 'completed presentation', which loosely relate to presentation_id, but fails to explain output_format options or idempotency_key usage.

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 ('Queue an export job') and the target resource ('for a completed presentation'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'tosea_list_exports' or 'tosea_redownload_export', which also relate to exports, so it misses full sibling distinction.

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 'tosea_list_exports' or 'tosea_redownload_export'. It mentions 'completed presentation' as a prerequisite but offers no explicit when/when-not rules or context for selection among export-related tools.

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/ToseaAI/mcp-ToseaAI'

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