Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RUNAPI_API_KEYNoYour RunAPI API key. Can also be set in ~/.config/runapi/config.json.

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
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

extend_videoB

Create a Veo 3.1 task on RunAPI (extend video). Returns a task id, status, and output URLs.

text_to_videoC

Create a Veo 3.1 task on RunAPI (text to video). Returns a task id, status, and output URLs.

upscale_videoC

Create a Veo 3.1 task on RunAPI (upscale video). Returns a task id, status, and output URLs.

get_taskB

Fetch the current status and latest result payload for a veo-3-1 task.

check_pricingC

Look up RunAPI pricing for the veo-3-1 model line.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a clearly distinct action: authentication (login), pricing lookup (check_pricing), task submission for three different video operations, and task polling (get_task). Although upscale_video, extend_video, and text_to_video all wrap the same RunAPI task-creation mechanism, their names and descriptions make the operation each performs unambiguous.

Naming Consistency4/5

The set predominantly follows a snake_case verb_noun pattern (upscale_video, extend_video, text_to_video, get_task, check_pricing). The bare 'login' verb is a minor deviation but still readable and conventional for auth.

Tool Count5/5

Six tools is a well-scoped set for a single-model video generation wrapper, with each tool earning its place (auth, three generation modes, task status, pricing). Nothing feels redundant or missing at the count level.

Completeness4/5

Core lifecycle is covered: authenticate, submit a task, and poll its status/result. Minor gaps exist, such as no task listing/cancellation and no image-to-video variant if the model line supports it, but agents can work around these using get_task and the returned output URLs.

Maintenance

ActivityMaintained
ResponsivenessNo issues