Skip to main content
Glama

gamma_create_from_template

Create a new presentation from a Gamma template by adapting your content and instructions to match the template's structure and design.

Instructions

Create a new gamma based on an existing template. Adapts content to match template structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesInstructions and content for adapting the template. Can include text and image URLs.
gammaIdYesID of the template gamma to base the new one on.
themeIdNoTheme ID to override template's theme.
exportAsNoExport format.
folderIdsNoFolder IDs to save the gamma to.
imageModelNoAI image model for new images.
imageStyleNoStyle for new AI-generated images.
Behavior2/5

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

No annotations provided. The description only says 'adapts content' without detailing behavioral aspects like permission requirements, rate limits, or what happens to the template.

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?

Single sentence, no redundancy. Could benefit from more structure (e.g., listing key parameters), but still concise.

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

Completeness1/5

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

With no output schema and no annotations, the description fails to explain return values, error conditions, or detailed behavior. Highly incomplete for a creation 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%, so the schema already documents all 7 parameters. The description adds minimal context ('adapts content') but does not significantly enhance parameter understanding.

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 verb 'create' and the resource 'gamma based on an existing template', distinguishing it from siblings like gamma_generate (generate from scratch) and listing tools.

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 guidance on when to use this tool versus siblings (e.g., gamma_generate). No mention of prerequisites or exclusions.

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