Skip to main content
Glama
Sign In
MCP VTEX Server

MCP VTEX Server

by leosepulveda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vtex_delete_price

Remove pricing data for specific SKUs in VTEX e-commerce platform to manage product listings and maintain accurate catalog information.

Instructions

Delete price for a SKU

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": {
      "skuId": "<skuId>"
    },
    "name": "vtex_delete_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuIdYesSKU ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Delete' implies a destructive mutation, but it doesn't specify whether this is permanent, requires specific permissions, affects related data, or has rate limits. The description lacks crucial context for a mutation 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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core action and target, making it efficient despite its brevity.

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 inadequate. It doesn't explain what happens after deletion (success response, error conditions), whether the action is reversible, or how it interacts with other price-related tools. The context is incomplete for safe and effective use.

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 skuId clearly documented. The description adds no additional parameter context beyond implying a price is deleted for that SKU. This meets the baseline for high schema coverage, but doesn't enhance understanding of the parameter's role.

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 clearly states the action ('Delete') and target resource ('price for a SKU'), making the purpose unambiguous. However, it doesn't differentiate from sibling deletion tools like vtex_delete_brand or vtex_delete_product, which follow the same pattern but target different resources.

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 guidance is provided on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an existing price), consequences of deletion, or when to choose this over related tools like vtex_create_or_update_price or vtex_get_price for price management.

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