Skip to main content
Glama
Sign In
vercel-mcp-pro

vercel-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_deployment

Need to stop a deployment that is building or queued? Cancel it by providing the deployment ID.

Instructions

Cancel an in-progress (BUILDING/QUEUED) deployment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "cancel_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDeployment id (dpl_...).
teamIdNoTeam ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
slugNoTeam slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, and the description discloses only that the tool cancels deployments in specific states. No mention of side effects, reversibility, authorization, or impact on associated resources.

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?

Extremely concise single sentence with no extraneous information. Effectively communicates the core action and constraint.

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?

Covers the main purpose but lacks details on return values, side effects, or additional context. Given no output schema, more behavioral context would be helpful.

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 100%, so the schema already documents all parameters. The description adds no additional parameter-level meaning, meeting the 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?

Clearly states the verb (cancel), resource (deployment), and specific state constraint (BUILDING/QUEUED). Distinguishes from sibling tools like delete_deployment and rollback_deployment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when or when not to use this tool. Does not compare to alternatives or provide usage context beyond the basic constraint.

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