Skip to main content
Glama

Price Tables Variants List

tiendanube_price_tables_variants_list
Read-onlyIdempotent

Lists the variants assigned to a specific price table so you can inspect which product variants use that table and review their pricing assignments.

Instructions

List variants assigned to a price table. HTTP: GET /products/price-tables/{table_id}/variants Required scope: read_products API version: 2025-03 Returns {count, page, per_page, total?, has_more, next_page?, items[]}.

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>"
    },
    "name": "tiendanube_price_tables_variants_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1). Orders: page * per_page must be <= 10000
fieldsNoComma-separated list of fields to return, to reduce payload size (e.g. 'id,name,variants')
per_pageNoItems per page (default 30, max 200; max 50 for external invoices)
table_idYesPrice table ID
response_formatNoOutput format: 'json' (default, full data) or 'markdown' (human-readable)json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the description doesn't need to re-assert safety. It does add genuinely new context: the read_products scope requirement, the pinned API version, and the paginated response envelope ({count, page, per_page, has_more, next_page, items[]}), which the agent would otherwise have to guess.

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?

Five short, front-loaded lines with no filler; the purpose is first and the operational metadata follows. The raw HTTP line and version tag are somewhat redundant for an agent but still cheap and diagnostically useful.

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

Completeness4/5

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

With no output schema present, the description usefully sketches the return envelope, and the required scope plus API version cover the main operational unknowns. Minor gaps remain around ordering of returned variants and whether values are price-table-specific overrides, but an agent can call it correctly from what's given.

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 paging, fields and response_format semantics are already fully documented in the schema. The description adds no parameter-level meaning beyond repeating the endpoint path and the shape of the response, so the baseline 3 applies.

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?

States a specific verb and resource with a scope qualifier ('variants assigned to a price table'), which implicitly separates it from the generic tiendanube_variants_list and from the sibling categories/customers sub-lists. It stops short of naming the alternative tools explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and endpoint but never spelled out: nothing says when to pick this over tiendanube_variants_list or price_tables_customers_list, nor any prerequisite beyond the scope requirement. The stated 'Required scope: read_products' is the only concrete gating information.

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