Skip to main content
Glama

Create video gift

create_gift

Create a personalized video gift from photos and an original song. Optionally render the film, consuming one prepaid credit and requiring consent that you hold rights to the photos and recipient's depiction.

Instructions

Create a personalized video gift from photos + an original song and (optionally) render the film. Rendering spends one prepaid credit and takes a few minutes — poll with get_gift, or watch list_gifts for status 'delivered'. You MUST pass consent=true to render (you attest you hold the rights to the photos and the recipient's depiction).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoFilm tier. Defaults to 'signature'.
styleNoRender style preset. Defaults to 'gift' (unchanged). 'social' biases delivery toward vertical 9:16; 'brand' is for branded gifts.
memoryNoA sentence or two the song can lean on.
renderNoRender the film now (spends one credit). If false, create a draft only. Defaults to false.
consentNoREQUIRED to render: you attest you hold the rights to these photos and the recipient's depiction.
occasionYesOccasion id from list_occasions, e.g. 'anniversary-video'. Drives the song and tone.
photo_urlsNoPublic image URLs of the recipient (up to 30). Required to render.
story_noteNoExtra context for the film's narrative.
relationshipYesRelationship to the recipient, e.g. 'my wife', 'grandpa', 'our team'.
feeling_wordsNoUp to 6 tone words, e.g. ['joyful','grateful','proud'].
recipient_nameYesWho the gift is for, e.g. 'Jamie'.
Behavior5/5

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

Despite no annotations, description discloses credit consumption, rendering time, and the need for consent. It also explains how to track delivery via polling or watching list_gifts.

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?

Three concise sentences: purpose, behavioral details, critical consent requirement. No wasted words, front-loaded information.

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?

Covers main workflow and key constraints for a complex multi-parameter tool. Lacks explicit mention of return value or that photo_urls are required for rendering (though schema states it). Still quite comprehensive.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. Description adds value by emphasizing the consent parameter's requirement and clarifying defaults (tier, style, render). Some parameter details are already in 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?

Description clearly states the tool creates a personalized video gift from photos and an original song, with optional rendering. It uses a specific verb and resource, distinguishing it from siblings like get_gift and list_gifts.

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

Usage Guidelines5/5

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

Explicit guidance on when to render (and spend credit) vs create a draft, with the requirement of consent=true for rendering. Also directs to poll with get_gift or watch list_gifts for status updates.

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/CryptoLibertus/myvideogift-mcp'

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