Skip to main content
Glama
cphoskins
by cphoskins

gamma_generate

Convert text into presentations, documents, webpages, or social posts. Submit your input, then poll for the finished share URL.

Instructions

Generate a Gamma presentation, document, webpage, or social post from text.

Generation is asynchronous. Returns a generationId; poll gamma_get_status until status is 'completed' or 'failed' to retrieve the share URL.

Args: input_text: Topic, outline, or full content (1-400000 chars). text_mode: How to interpret input — 'generate' (expand), 'condense', or 'preserve' (keep as-is). Default 'generate'. format: Output type — 'presentation', 'document', 'social', or 'webpage'. Omit to use Gamma's default. theme_id: Theme ID from gamma_list_themes. Omit for default theme. num_cards: Target card count (minimum 1, plan-dependent maximum). 0 = let Gamma decide. card_split: 'auto' or 'inputTextBreaks' (splits on blank lines in input). additional_instructions: Extra style/content guidance (max 5000 chars). export_as: Auto-export format — 'pdf', 'pptx', or 'png'. Empty for no export. folder_ids: Workspace folder IDs to place the output in (max 10). Use gamma_list_folders to discover IDs. text_options: Nested object with 'amount' (brief|medium|detailed|extensive), 'tone' (string, max 500 chars), 'audience' (string, max 500 chars), 'language' (ISO code, e.g. 'en', 'es', 'fr'). image_options: Nested object with 'source' (aiGenerated, pictographic, unsplash, webAllImages, webFreeToUse, webFreeToUseCommercially, giphy, pexels, placeholder, noImages, themeAccent), 'model' (e.g. 'dall-e-3', 'imagen-4-ultra', 'flux-2-pro'), 'style' (string, max 500 chars). card_options: Nested object with 'dimensions' (fluid, 16x9, 4x3, pageless, letter, a4, 1x1, 4x5, 9x16 — must match format) and 'headerFooter' (6-position layout with logos, card numbers, or text). sharing_options: Nested object with 'workspaceAccess' (noAccess, view, comment, edit, fullAccess), 'externalAccess' (noAccess, view, comment, edit), and 'emailOptions' ({recipients: [...], access: ...}).

Call gamma_describe_options to inspect accepted enum values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_textYes
text_modeNogenerate
formatNo
theme_idNo
num_cardsNo
card_splitNo
additional_instructionsNo
export_asNo
folder_idsNo
text_optionsNo
image_optionsNo
card_optionsNo
sharing_optionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses asynchronous behavior, polling requirement, and parameter constraints (e.g., char limits, folder count). Without annotations, it carries the full burden and provides substantial behavioral insight beyond the schema.

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?

The description is structured with a clear lead sentence, followed by an async note and a detailed parameter list. While thorough, it is lengthy and could benefit from earlier mention of core workflow (generate, poll, retrieve).

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?

The description covers the full workflow (async generation, polling, retrieval) and references sibling tools (gamma_get_status, gamma_describe_options). It lacks only a direct comparison to gamma_generate_from_template, but the output schema exists, reducing the need for return-value details.

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

Parameters5/5

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

With 0% schema coverage, the description compensates fully by detailing each parameter's purpose, allowable values, defaults, and nested structures (e.g., text_options, image_options). Examples and constraints (max 5000 chars, min 1 card) add clarity the schema lacks.

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 tool generates various Gamma outputs from text. However, it does not differentiate from the sibling gamma_generate_from_template, leaving ambiguity about when to use this tool versus the template-based alternative.

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?

No explicit guidance on when to use this tool, when not to, or alternatives. It references gamma_describe_options for enum values but lacks context on decision-making between this and sibling tools like gamma_generate_from_template.

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/cphoskins/gamma-app-mcp'

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