Skip to main content
Glama
Arkava-AI
by Arkava-AI

Generate Gamma Content

gamma_generate

Generates presentations, documents, webpages, or social posts from any text prompt using AI. Automatically structures, designs, and styles content.

Instructions

Create a new presentation, document, webpage, or social post using Gamma's AI.

This tool generates professional content from any text input - a one-line prompt, messy notes, or polished content. Gamma's AI will structure, design, and style your content automatically.

SUPPORTED FORMATS:

  • presentation: Slide decks (sizes: fluid, 16x9, 4x3)

  • document: Reports, articles, essays (sizes: fluid, pageless, letter, a4)

  • webpage: Websites with header/footer support (size: fluid)

  • social: Social media posts (sizes: 1x1, 4x5, 9x16)

PARAMETERS:

  • prompt (required): Your content or instructions. Can be brief ("Company overview presentation") or detailed with bullet points.

  • format (required): One of presentation, document, webpage, social

  • cards: Number of slides/sections (1-60, default: AI-determined)

  • size: Aspect ratio appropriate for the format

  • themeId: Visual theme ID (use gamma_list_themes to see options)

  • language: Target language code (en, es, fr, de, zh, ja, etc.)

  • imageStyle: auto, photographic, generated, clipart, none

  • cardDensity: auto, high, low

  • waitForCompletion: If true, waits up to 5 min for generation to complete

RETURNS:

  • generationId: ID for tracking/status checks

  • status: pending, completed, or failed

  • url: Link to view content (when completed)

  • title: Generated or custom title

EXAMPLES:

  1. Quick presentation: { prompt: "5 slide pitch deck for AI startup", format: "presentation" }

  2. Detailed document: { prompt: "Technical documentation for REST API...", format: "document", cards: 10 }

  3. Styled content: { prompt: "Company culture overview", format: "presentation", themeId: "theme_123", waitForCompletion: true }

CREDITS: Each generation consumes Gamma API credits based on complexity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate a non-read-only, non-destructive action. The description adds valuable behavioral context: generation consumes credits, waitForCompletion behavior, default AI-determined card count, and return status. No contradiction with annotations.

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 well-structured with sections for formats, parameters, returns, and examples. It is front-loaded with the primary action. While comprehensive, it remains clear and easy to scan, though it could be slightly tighter.

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, the description covers return fields (generationId, status, url, title). It addresses formats, sizes, parameters, and credits. It misses error handling or authentication details but is sufficient for proper invocation.

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?

The input schema is empty (0 parameters, 100% coverage), so the description carries the full burden. It thoroughly explains all parameters, including required ones, options, defaults, and examples, which is far beyond the schema.

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 the tool creates new presentations, documents, webpages, or social posts. It specifies the verb 'create' and lists supported resources, distinguishing it from sibling tools like gamma_from_template and gamma_list_themes.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool (creating new content from text) and references gamma_list_themes for theme selection. It lacks explicit exclusions or alternatives for some siblings, but examples and parameter descriptions give adequate guidance.

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/Arkava-AI/gamma-mcp-server'

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