Skip to main content
Glama
runpod

RunPod MCP Server

Official
by runpod

create-endpoint

Creates a serverless endpoint on RunPod. Configure Docker image, GPU pool, autoscaling with min/max workers, idle timeout, and environment variables.

Instructions

Create a Serverless endpoint. On v2 (default), pass an inline config: imageName + gpuPoolIds (GPU pool names from list-gpu-types — the pool field, e.g. AMPERE_80/ADA_24) plus optional workers/scaling/disk/env. On v1, pass a templateId instead. Worker min/max set autoscaling bounds (min 0 = scale to zero).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNoEnvironment variables (v2)
argsNoContainer start command/args (v2)
nameNoName for the endpoint
portsNoPorts to expose (v2), e.g. ['8000/http']
gpuCountNoGPUs per worker (v2)
flashbootNoFlashBoot mode (v2)
imageNameNoDocker image (v2). Required on v2 instead of a templateId.
gpuPoolIdsNoGPU pool names (v2, required). The `pool` field from list-gpu-types, e.g. ["AMPERE_80"]. NOT GPU type ids.
gpuTypeIdsNoList of acceptable GPU types (v1)
scalerTypeNoAutoscaler type
templateIdNoTemplate ID (v1). Required on v1.
workersMaxNoMaximum number of workers
workersMinNoMinimum number of workers
computeTypeNoGPU or CPU endpoint (v1)
idleTimeoutNoIdle timeout in seconds before scaling a worker down
scalerValueNoAutoscaler target value
dataCenterIdsNoList of preferred data centers
networkVolumeIdsNoNetwork volume ids to attach (v2)
containerDiskInGbNoContainer disk size in GB (v2)
executionTimeoutMsNoPer-job execution timeout in ms (v2)
containerRegistryAuthIdNoContainer registry auth id for a private image (v2)
Behavior4/5

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

Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true. The description adds context about version-dependent parameters and autoscaling behavior (scale to zero), which goes beyond annotations. No contradictions.

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 two sentences, immediately stating the purpose, then concisely covering version-specific configurations and autoscaling. 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 21 parameters, no output schema, and rich annotations, the description covers core logic (v2 vs v1), key parameters, and autoscaling. It references list-gpu-types for pool names. Missing explanations of default values or error scenarios, but overall complete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3, but the description adds high-value clarifications: connecting gpuPoolIds to list-gpu-types pool field (not GPU type ids), explaining worker min/max as autoscaling bounds, and grouping parameters by version. This significantly aids correct invocation.

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 'Create a Serverless endpoint' and distinguishes between v2 (inline config with imageName + gpuPoolIds) and v1 (templateId), making the purpose specific and distinct from sibling tools like create-pod or update-endpoint.

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 v2 vs v1, and explains that worker min/max set autoscaling bounds (min 0 = scale to zero). However, it lacks explicit when-not-to-use or alternative tool references (e.g., update-endpoint for modifications).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runpod/runpod-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server