Skip to main content
Glama

gamma_generate

Generate presentations, documents, social posts, or webpages from text input. Control format, length, tone, and images to match your needs.

Instructions

Generate a new presentation, document, social post, or webpage from text input. Returns a generationId to poll for completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format type.presentation
themeIdNoTheme ID to use. Get from gamma_list_themes.
exportAsNoExport format. Links expire, download promptly.
numCardsNoNumber of cards/slides to generate (1-60 for Pro, 1-75 for Ultra).
textModeYesHow to handle input text. 'generate' expands, 'condense' summarizes, 'preserve' keeps as-is.
textToneNoTone/voice of content (e.g., 'professional, inspiring').
cardSplitNoHow to split content into cards. 'auto' uses numCards, 'inputTextBreaks' uses \n---\n markers.auto
folderIdsNoFolder IDs to save the gamma to.
inputTextYesContent to generate from. Can include text and image URLs. Max ~100k tokens.
dimensionsNoCard dimensions. Presentation: fluid/16x9/4x3. Document: fluid/pageless/letter/a4. Social: 1x1/4x5/9x16.
imageModelNoAI image model (if imageSource is 'aiGenerated'). E.g., 'flux-1-pro', 'imagen-4-pro'.
imageStyleNoImage style description (e.g., 'photorealistic', 'minimal line art').
textAmountNoHow much text per card.
imageSourceNoWhere to source images from.aiGenerated
textAudienceNoTarget audience description.
textLanguageNoOutput language code (e.g., 'en', 'es', 'fr').en
additionalInstructionsNoExtra instructions for generation (max 2000 chars).
Behavior3/5

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

No annotations are provided, so the description carries full burden. It correctly mentions asynchronous generation and polling, and export link expiration from the schema. However, it omits auth requirements, rate limits, and error handling.

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?

Two sentences with no wasted words. The first sentence defines the action, the second specifies the return value and polling need. Efficient and front-loaded.

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?

With 17 parameters and no output schema or annotations, the description is too brief. It fails to explain the generation workflow, asynchronous nature, or provide examples. The parameter descriptions in the schema are thorough, but the tool description itself is incomplete for a complex tool.

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% with individual parameter descriptions. The tool description adds minimal parameter context beyond stating the return value. It does not elaborate on parameter interactions or behaviors.

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?

Description clearly states it generates presentations, documents, social posts, or webpages from text input, and returns a generationId. This distinguishes it from siblings like gamma_create_from_template (template-based) and gamma_get_generation (polling).

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?

The description implies a polling workflow by mentioning returns a generationId, but does not explicitly state when to use this tool versus alternatives. Sibling tools exist for templates and polling, but no direct guidance is provided.

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/Purple-Horizons/gamma-mcp'

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