MCP VTEX Server

vtex_create_promotion

Create promotional campaigns for VTEX e-commerce stores by setting discounts, dates, and activation parameters to drive sales.

Instructions

Create a new promotion

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": {
      "name": "<name>",
      "beginDateUtc": "<beginDateUtc>",
      "endDateUtc": "<endDateUtc>"
    },
    "name": "vtex_create_promotion"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Promotion name
`beginDateUtc`	Yes	Start date (ISO 8601)
`endDateUtc`	Yes	End date (ISO 8601)
`description`	No	Promotion description
`isActive`	No	Promotion active status
`type`	No	Promotion type
`percentualDiscountValue`	No	Percentage discount
`nominalDiscountValue`	No	Fixed amount discount

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 the full burden of behavioral disclosure. 'Create a new promotion' implies a write operation but doesn't mention required permissions, whether promotions are immediately active, if there are rate limits, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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 sentence with zero wasted words. It's appropriately sized and front-loaded, immediately conveying the core purpose without unnecessary elaboration.

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 mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects like permissions, side effects, or response format, leaving significant gaps in understanding how to use this tool effectively.

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 schema already documents all 8 parameters thoroughly with descriptions, enums, and defaults. The description adds no parameter information beyond what's in the schema, meeting the baseline of 3 when schema coverage is high.

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 ('Create') and resource ('promotion'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'vtex_create_coupon' or 'vtex_create_product', which follow the same 'Create a new X' pattern, so it lacks sibling distinction.

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 siblings like 'vtex_create_coupon' and 'vtex_update_promotion', there's no indication of when promotions are appropriate versus coupons or when to create versus update. No prerequisites or exclusions are mentioned.

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

Deploy Server