Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vercel_create_deployment

Create Vercel preview deployments to test changes before production. Redeploy an existing commit or deploy fresh from git, with an option to skip the build cache.

Instructions

Create a Vercel preview deployment. Direct production creation is disabled: production must use the canonical Safe Beta delivery rail with shared exact-SHA admission, staged smoke, promotion proof, and a terminal receipt. Pass deployment_id to redeploy an existing commit, or project_id + git_ref to deploy fresh from git. Set force_new=true to skip the build cache.

Input Schema

NameRequiredDescriptionDefault
nameNo
gitRefNoAlias for git_ref.
targetNoUse 'preview'. 'production' is refused and must use the canonical delivery rail.
teamIdNoAlias for team_id.
api_keyNo
git_refNoBranch or SHA to deploy. Defaults to 'main'.
team_idNo
forceNewNoAlias for force_new.
force_newNoSkip build cache. Default false.
projectIdNoAlias for project_id.
project_idNoDeploy fresh from the project's linked git repo.
deploymentIdNoAlias for deployment_id.
deployment_idNoRedeploy the git source of this existing deployment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.11
    • addedInput schema / properties / deploymentId
      Added value: +{
+  "description": "Alias for deployment_id.",
+  "type": "string"
+}
    • addedInput schema / properties / forceNew
      Added value: +{
+  "description": "Alias for force_new.",
+  "type": "boolean"
+}
    • addedInput schema / properties / gitRef
      Added value: +{
+  "description": "Alias for git_ref.",
+  "type": "string"
+}
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Alias for project_id.",
+  "type": "string"
+}
    • changedInput schema / properties / target / description
      Previous value: -"'production' (default) or 'preview'."New value: +"Use 'preview'. 'production' is refused and must use the canonical delivery rail."
    • addedInput schema / properties / teamId
      Added value: +{
+  "description": "Alias for team_id.",
+  "type": "string"
+}
  2. Addedv0.1.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most important non-obvious behavior: production targets are refused here, and redeploy vs fresh-build paths differ. It omits authentication requirements (an api_key parameter exists) and what the call returns, but the core operational constraints are stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope statement is front-loaded and the mode choice is clear, but the 'canonical Safe Beta delivery rail with shared exact-SHA admission, staged smoke, promotion proof, and a terminal receipt' clause is dense internal jargon that consumes space without helping the agent decide how to call this tool.

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?

For a 13-parameter mutation with no annotations and no output schema, the description covers the key routing decision but leaves several parameters (name, team_id, api_key) undocumented in both schema and description, and says nothing about permissions or failure behavior.

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

Parameters3/5

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

Schema coverage is 77%, so the schema already documents most fields including the two deployment strategies and force_new. The description reinforces the deployment_id vs project_id + git_ref choice and the cache-skip flag but adds no syntax, defaults, or precedence rules beyond the schema text.

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?

States a specific verb and resource ('Create a Vercel preview deployment') and immediately bounds the scope to preview, distinguishing it from production deployment paths. An agent knows exactly what this tool produces without opening the schema.

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 production creation is disabled and must go through the canonical delivery rail, and gives the two invocation modes (deployment_id to redeploy vs project_id + git_ref for a fresh build). It does not name a concrete sibling tool for production, but no production-deploy sibling exists in the toolset, so the guidance is effectively complete.

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

Deploy Server

Other Tools