Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AIGIFMAKER_API_KEYYesYour AI GIF Maker API key, created at https://aigifmaker.ai/settings/apikeys. Required to authenticate with your account.
AIGIFMAKER_BASE_URLNoOverrides the API endpoint. Only useful against a local build of the site.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_gifA

Turn a text prompt into an animated GIF on AI GIF Maker (aigifmaker.ai) and return the GIF URL. Native GIF generation, no video conversion; usually about a minute. Costs 1 credit on the AI GIF Maker account behind AIGIFMAKER_API_KEY, the same as on the website.

check_gifA

Look up a GIF by the task id generate_gif returned when it was still running, and return its URL once it is ready. Free to call.

check_creditsA

Credits left on the AI GIF Maker account behind AIGIFMAKER_API_KEY. One GIF costs 1 credit. Free to call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct action on a distinct concern: generate_gif creates a job, check_gif polls a specific job by task id, and check_credits reads account balance. There is no plausible way to confuse one with another, and the descriptions make the generation-then-poll flow explicit.

Naming Consistency5/5

All three tools follow the same verb_noun snake_case pattern (generate_gif, check_gif, check_credits), with the shared 'check_' prefix clearly grouping the two read-only/free operations.

Tool Count4/5

Three tools is at the lean end but each earns its place: generation, async polling, and credit lookup are all necessary for the stated workflow. Nothing extraneous, though the surface is thin enough that any addition (cancel, history) would round it out.

Completeness4/5

The core lifecycle is covered end to end: submit a prompt, retrieve the result asynchronously, and verify the account has credits before spending. Minor gaps exist — no way to cancel or delete a job, list past GIFs, or check status without the task id — but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues