vercel-mcp-pro

delete_project

Permanently delete a Vercel project. This action is irreversible and cannot be undone.

Instructions

Delete a project permanently. This cannot be undone.

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": {
      "idOrName": "<idOrName>"
    },
    "name": "delete_project"
  }
}

Input Schema

Name	Required	Description
`idOrName`	Yes	Project id or name.
`teamId`	No	Team ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
`slug`	No	Team slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses the critical behavioral trait of permanent deletion ('cannot be undone'), which is essential. Without annotations, it carries the full burden; however, it does not cover authorization needs or side effects on related resources, so not a 5.

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 extremely concise with two short sentences, front-loading the action and irreversibility. Every word earns its place with no redundancy.

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?

For a simple deletion tool with no output schema and full parameter descriptions, the description covers the key effect (permanence). However, it omits return value or post-deletion state, which would be helpful, but overall adequate.

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 description coverage is 100%, so the input schema already documents all three parameters sufficiently. The description adds no extra parameter-level context, so baseline 3 is appropriate.

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 the tool permanently deletes a project, using specific verb 'delete' and resource 'project', and distinguishes it from sibling tools like update_project or pause_project by emphasizing irreversibility.

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

Usage Guidelines3/5

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

The description implies when to use (when permanent deletion is intended) but lacks explicit guidance on when not to use or alternatives like pausing or deactivating. No mention of prerequisites or context compared to similar tools.

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

Deploy Server