gamma-app-mcp

Overview Schema Source Related Servers Discussions Admin

gamma_generate_from_template

Generate a new variant from a Gamma template by replacing content while preserving layout. Use for batch creations like investor decks or LinkedIn cards with consistent branding.

Instructions

Generate a variant from an existing Gamma template with swapped content.

Uses POST /generations/from-template. The template Gamma must have exactly one Page. Layout is preserved; new content is generated from the prompt. Ideal for batch content with consistent branding — per-segment investor decks, per-lead LinkedIn cards, rebranded decks per channel partner.

Args: prompt: Content description for the new variant (1-400000 chars). gamma_id: The Gamma ID of the template file (required). theme_id: Optional theme ID to override the template's theme. image_options: Same shape as gamma_generate's image_options. sharing_options: Same shape as gamma_generate's sharing_options. folder_ids: Workspace folder IDs to place the output in (max 10). export_as: Auto-export format — 'pdf', 'pptx', or 'png'.

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": {
      "prompt": "<prompt>",
      "gamma_id": "<gamma_id>"
    },
    "name": "gamma_generate_from_template"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes
`gamma_id`	Yes
`theme_id`	No
`image_options`	No
`sharing_options`	No
`folder_ids`	No
`export_as`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 27, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, description carries full burden. Discloses layout preservation, content generation, single-page template requirement, and limits (max 10 folder IDs). Does not mention auth or rate limits, but covers core behavioral traits.

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?

Concise and well-organized. One sentence summary, endpoint reference, usage guidance, then parameter block. No redundant words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no annotations, and presence of output schema (not shown but sufficient), description covers all necessary aspects: purpose, usage, parameter docs, and behavioral constraints. References sibling tool for shared parameter shapes. Complete and self-contained.

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?

Schema has 0% description coverage; description compensates fully. Each parameter gets a meaningful description: prompt length constraint, gamma_id required, theme_id optional, image_options/sharing_options reference to sibling tool, folder_ids cap, export_as enum values. Adds crucial context beyond schema types.

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?

Clear verb-resource pairing: 'Generate a variant from an existing Gamma template with swapped content.' Specifies the endpoint and constraint (template must have exactly one page). Distinguishes from sibling gamma_generate by focusing on template reuse.

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?

Provides ideal use cases: 'batch content with consistent branding' with examples. Does not explicitly state when not to use or name alternatives, but context implies contrast with gamma_generate for scratch generation.

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

Deploy Server