emaki
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMAKI_API_KEY | Yes | Your emaki API key. Create one at https://emaki.ai/settings/apikeys. | |
| EMAKI_BASE_URL | No | Overrides the 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_videoA | Generate a video clip from a text prompt on emaki.ai, or animate a still by passing image_url (image to video). Defaults to Seedance 2.5 (4 to 30 seconds, sound in the same pass). Runs on your emaki credits, the same price as on the website. Video takes minutes: by default this returns a run id to poll with check_status. |
| generate_imageA | Generate an image from a text prompt on emaki.ai and return its URL. Defaults to Nano Banana 2 Lite, the lowest-cost model; a good way to make a first frame for generate_video. Runs on your emaki credits. |
| check_statusA | Read the status of a run started with generate_video or generate_image, and its URL when it is ready. |
| creditsA | The credits left on the emaki account behind EMAKI_API_KEY. Free to call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: credits reads balance, generate_video/generate_image produce different media types, and check_status polls async runs. No two tools can be reasonably confused for one another.
Three of four tools follow a clean verb_noun pattern (generate_video, generate_image, check_status). The outlier is 'credits', a bare noun that breaks the pattern but remains unambiguous.
Four tools is a tight, well-scoped surface for a generation service. Each earns its place: two generators, one async poller required by the async design, and one account query.
The generate-then-poll lifecycle is covered end to end, plus credit awareness. Minor gaps exist (no list/history of past runs, no cancel or delete for an in-flight run), but the core workflow has no dead ends.