MCP VTEX Server

vtex_delete_category

Remove a category from your VTEX e-commerce catalog by specifying its ID. This tool helps maintain organized product structures by deleting outdated or unnecessary categories.

Instructions

Delete a category

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": {
      "categoryId": "<categoryId>"
    },
    "name": "vtex_delete_category"
  }
}

Input Schema

Name	Required	Description	Default
`categoryId`	Yes	Category ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify whether this is permanent, requires specific permissions, has side effects (e.g., on related products), or provides confirmation. This leaves critical behavioral gaps for a destructive operation.

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, efficient phrase with zero wasted words. It's appropriately sized for a simple operation and front-loads the essential action, making it easy to parse quickly.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It lacks critical context such as success/error behavior, return values, permissions required, or irreversible consequences, leaving the agent with significant uncertainty about tool 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?

The input schema has 100% description coverage, with the single parameter 'categoryId' documented as 'Category ID to delete.' The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for adequate but not additive semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a category' clearly states the action (delete) and resource (category), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'vtex_delete_brand' or 'vtex_delete_product' beyond the resource type, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'vtex_update_category' and 'vtex_get_category' available, there's no indication of prerequisites (e.g., whether the category must be empty) or when deletion is appropriate versus archiving or updating.

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

Deploy Server