Skip to main content
Glama

create_deployment

Deploy a project using a Git source or inline files. Specify target environment: production, preview, or staging.

Instructions

Create a new deployment. The simplest path is to deploy from a connected Git source: pass name (project) and a gitSource ({ type, repoId/org+repo, ref }). For file-based deploys, provide files. For most workflows the /vercel CLI skill is easier — use this when you need API-driven, headless deploys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name this deployment belongs to.
projectNoProject id (if different from name).
targetNoDeploy target.
gitSourceNoGit source, e.g. { type: 'github', repoId: 123, ref: 'main' } or { type:'github', org, repo, ref }.
filesNoInline files [{ file, data }] for file-based deploys.
metaNoArbitrary metadata key/values.
projectSettingsNoOverride project build settings.
teamIdNoTeam ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
slugNoTeam slug to scope the request (alternative to teamId).
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose potential side effects, required permissions, rate limits, or what happens during deployment creation (e.g., triggers build, impacts existing deployments).

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?

Three sentences, front-loaded with main purpose, no unnecessary words or repetition. Every sentence serves a clear function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Moderate completeness for a creation tool. Lacks details on return value or how to monitor deployment status, which would help the agent, but given the schema coverage and context, it's adequate.

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% with descriptions, baseline 3. Description adds value by explaining the simplest path (gitSource vs files) and gives example structure, exceeding baseline.

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?

Clear verb 'Create' with specific resource 'deployment'. Distinguishes two methods (Git source and file-based) and mentions alternative Vercel CLI, differentiating from sibling tools.

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?

Explicitly states when to use this tool (API-driven, headless deploys) and for most workflows recommends the CLI skill instead. Provides clear context but lacks explicit 'when not to use' beyond the CLI recommendation.

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/helbertparanhos/vercel-mcp-pro'

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