vercel-mcp-pro

update_edge_config_items

Manage Edge Config items by creating, updating, upserting, or deleting them in a single PATCH request.

Instructions

Upsert/delete items in an Edge Config in one PATCH. Pass operations [{ operation:'create'|'update'|'upsert'|'delete', key, value? }].

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": {
      "edgeConfigId": "<edgeConfigId>",
      "items": "<items>"
    },
    "name": "update_edge_config_items"
  }
}

Input Schema

Name	Required	Description
`edgeConfigId`	Yes	Edge Config id (ecfg_...).
`items`	Yes	Item operations to apply.
`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

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral details. It correctly indicates mutation via 'PATCH' and lists operation types, but does not explain error scenarios, idempotency, or effects on unspecified items.

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 a single, focused sentence that front-loads the core action and format. Every word is necessary and no information is repeated.

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?

The description omits return format, prerequisites (e.g., existence of Edge Config), and any atomicity guarantees. For a tool with 4 parameters and no output schema, the description is adequate but lacks completeness.

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?

With 100% schema coverage, the baseline is 3. The description adds value by specifying the structure of the 'items' parameter (array of objects with operation, key, value?), which goes beyond the schema's generic description.

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 verb ('Upsert/delete'), the resource ('items in an Edge Config'), and the method ('in one PATCH'), which distinguishes it from sibling tools like 'get_edge_config_items' and 'delete_edge_config'.

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 use for batch operations on Edge Config items but does not explicitly mention when to use it versus alternatives or any prerequisites. The sibling tool list provides context, but the description lacks direct guidance.

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

Deploy Server