Skip to main content
Glama

pictify_generate_video_template

Generate a new video template from a text prompt using AI. The service designs a motion brief (palette, beats, typography), writes the scene as code, compiles it, renders preview frames and visually reviews them — then saves a draft template whose text, colors and optional image are editable variables. Use when the user wants a NEW video design; to re-render an existing template with different values, use pictify_render_video instead. Takes 30-60 seconds and is metered as one render. Returns the template UID and a preview image URL; render it with pictify_render_video, or refine it in the studio.

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>",
      "context": "<context>"
    },
    "name": "pictify_generate_video_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNoCanvas width in pixels
heightNoCanvas height in pixels
promptYesWhat the video is for, with any mood/style guidance. Example: 'An 8 second product launch teaser for a developer tool called ShipFast — dark, electric, type-driven'
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
brandColorNoOptional brand color (hex) to build the palette around, e.g. '#ff5533'
durationSecondsNoVideo length in seconds (1-60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the entire pipeline (designs motion brief, writes code, compiles, renders preview frames, visually reviews), performance (30-60 seconds), metering (one render), and result format (UID and preview URL). This is far beyond what schema alone offers.

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?

The description is compact and front-loaded. Each sentence serves a distinct purpose: function, process, usage guidance, timing, and return value. No redundant or filler content.

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 no output schema, the description fully explains return values (UID, preview URL) and next steps (render with pictify_render_video or refine in studio). It also covers process, timing, cost metering, and alternatives, making it complete for a complex AI generation 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 baseline is 3. The description mentions 'text, colors and optional image are editable variables', but that describes output template variables, not input parameters. It does not add meaningful specifics for width, height, brandColor, or durationSeconds beyond the schema descriptions.

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's action and resource: 'Generate a new video template from a text prompt using AI.' It also distinguishes itself from siblings by emphasizing that it creates a NEW video design, and explicitly contrasts with pictify_render_video for re-rendering.

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?

Provides explicit usage guidance: 'Use when the user wants a NEW video design; to re-render an existing template with different values, use pictify_render_video instead.' This specifies when to use the tool and names the alternative, making the selection unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.