Skip to main content
Glama
pictify-io

Pictify MCP Server

by pictify-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pictify_create_gif

Create animated GIFs from HTML content with CSS animations, webpage URLs, or saved templates for banners, demos, logos, and social media content.

Instructions

Create an animated GIF from HTML content with CSS animations, a URL, or a template. The HTML must contain CSS @keyframes animations, transitions, or JavaScript animations to produce frames. Common use cases: animated banners, loading spinners, product demos, social media animations, animated logos, and eye-catching ad creatives. Provide ONE of: 'html' (custom animated HTML/CSS), 'url' (capture from webpage), or 'template' + 'variables' (render a saved template). For recording a GIF from a live website over a specified duration, use pictify_capture_gif instead. Returns the hosted GIF URL and animation duration. Maximum dimensions: 2000x2000 pixels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoHTML content with CSS animations to render as an animated GIF. Must include CSS @keyframes or transitions for animation. Mutually exclusive with 'url' and 'template'.
urlNoURL of a web page to capture as a GIF. Mutually exclusive with 'html' and 'template'.
templateNoTemplate UID to render as a GIF. Use with 'variables'. Mutually exclusive with 'html' and 'url'.
variablesNoTemplate variables as key-value pairs. Only used when 'template' is provided.
widthNoGIF width in pixels (1-2000). Keep dimensions reasonable for file size.
heightNoGIF height in pixels (1-2000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses required animation content, maximum dimensions, and return values, but omits authentication needs, rate limits, or side effects.

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 well-structured, each sentence adds value, and it is appropriately sized for the tool's complexity with no wasted words.

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 the absence of an output schema, the description adequately covers return values, input constraints, and usage patterns. It lacks details on persistence or error conditions but is largely complete for a creation tool.

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 coverage is 100%, so baseline is 3. The description adds mutual exclusivity context, template variable dependency, and practical limits like dimension maximums, elevating it above mere schema repetition.

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 it creates an animated GIF from HTML, URL, or template, and explicitly distinguishes from pictify_capture_gif for live website recording.

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 explicit guidance on when to use each parameter (one of html, url, template+variables) and directs to an alternative for live recording. It lists common use cases but doesn't cover all sibling exclusions.

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

Deploy Server

Other Tools