Skip to main content
Glama

Price Tables Variants Add

tiendanube_price_tables_variants_add

Assign product variants to a Tiendanube price table to control which variants use its pricing.

Instructions

Assign variants to a price table. Body shape per the API reference. HTTP: POST /products/price-tables/{table_id}/variants Required scope: write_products API version: 2025-03

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": {
      "table_id": "<table_id>",
      "payload": "<payload>"
    },
    "name": "tiendanube_price_tables_variants_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesRequest body (object or array)
table_idYesPrice table ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive open-world write, so the safety profile is covered. The description adds genuinely useful context the annotations don't carry, namely the required write_products scope and the exact endpoint, but it says nothing about what happens when a variant is already in the table or whether the payload replaces existing assignments.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded with the operation before the mechanics. Every line carries information, though 'Body shape per the API reference' is a pointer with no payload and earns its place only weakly.

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 whose only real input is a free-form body and which has no output schema, the description leaves out the payload shape, the duplicate/conflict behavior, and the response content. An agent would know the endpoint but not what to put in the request or what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is technically 100%, but the payload parameter is an opaque, loosely-typed anyOf with the sole description 'Request body (object or array)'. The description's 'Body shape per the API reference' defers the entire payload contract to an external document an agent may not have, so it does not compensate for the schema's lack of semantic detail despite the high nominal coverage.

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 gives a specific verb and resource: 'Assign variants to a price table', which an agent can distinguish from the sibling list/update/remove variants tools by intent. It stops short of explicitly naming how it differs from tiendanube_price_tables_variants_update, so sibling differentiation is only implicit.

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?

There is no guidance on when to use this versus tiendanube_price_tables_variants_update or _remove, nor any prerequisite statement beyond the OAuth scope. The required scope and HTTP verb are stated, but that describes the call mechanics rather than when to choose this tool.

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