MCP VTEX Server

vtex_create_product

Add new products to your VTEX e-commerce catalog by specifying name, category, brand, and other essential details for online store management.

Instructions

Create a new product in VTEX catalog

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>",
      "CategoryId": "<CategoryId>",
      "BrandId": "<BrandId>"
    },
    "name": "vtex_create_product"
  }
}

Input Schema

Name	Required	Description
`Name`	Yes	Product name
`CategoryId`	Yes	Category ID
`BrandId`	Yes	Brand ID
`LinkId`	No	Product URL slug
`RefId`	No	Product reference ID
`Description`	No	Product description
`IsVisible`	No	Product visibility
`IsActive`	No	Product active status

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create a new product' implies a write operation, but it doesn't mention authentication requirements, potential side effects (like inventory creation), rate limits, error conditions, or what happens on success. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 that states the core purpose without any wasted words. It's appropriately sized for a tool with a clear primary function and gets straight to the point.

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 no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation, what permissions are needed, how to handle errors, or the relationship to sibling tools. The 100% schema coverage helps with parameters, but the overall context for using this tool effectively is lacking.

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 with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('new product in VTEX catalog'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like vtex_create_sku or vtex_update_product, which would require more specific context about when to create a product versus other catalog entities.

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_update_product, vtex_create_sku, and vtex_list_products, there's no indication of prerequisites, typical workflows, or when this creation tool is appropriate versus other operations on products or related entities.

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

Deploy Server