Skip to main content
Glama

Export to a web page

export_html

Exports a GlideDeck presentation to one self-contained HTML file that plays in any browser with the same camera moves, transitions, builds, parallax, and effects; videos are copied to a media folder.

Instructions

Exports the presentation to a single self-contained .html file that plays the show in any browser exactly like the app: the same camera moves, transitions, builds, parallax and effects, with text as vector outlines (no fonts needed) and images embedded. Videos are copied to a <name>_media folder next to it. Defaults to the project's name with .html.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "export_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNo
pathYesThe GlideDeck project file (.glide.json). Absolute, or relative to the server's folder; `.glide.json` is added when there is no extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and openWorldHint=false; the description adds real behavioral detail beyond this: text is converted to vector outlines (no font dependencies), images are embedded, and videos are written to a separate `<name>_media` folder beside the output. That side-effect disclosure is valuable for a write tool. It still omits overwrite/conflict behavior and what is returned on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core result, then progressively adds fidelity and side-effect details; nearly every clause carries information. The trailing sentence about the default name is a fragment and the media-folder note slightly interrupts the output-description flow, but nothing is filler.

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?

With no output schema, the description does the work of telling the agent what the call produces (an .html file plus a media folder) and how default naming works. Adequate for a two-parameter export tool, though it could state whether existing files are overwritten and what the response contains.

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 50%: `path` is documented in the schema but `out` has no schema description at all. The description partially compensates by explaining that the output defaults to the project's name with .html, which conveys that `out` is a name/path for the generated file. It still leaves ambiguous whether `out` accepts a full path, a directory, or just a basename.

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?

States a specific verb (Exports) and resource (the presentation) plus the exact artifact produced: a single self-contained .html file. The format naming inherently separates it from export_pdf/export_pptx siblings, and the fidelity note ('plays the show in any browser exactly like the app') further pins down what kind of export this is.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: choosing this tool when a browser-playable, font-free artifact is wanted. There is no explicit when-to-use versus export_pdf/export_pptx, and no prerequisites or exclusions (e.g., when html export loses fidelity).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.