Skip to main content
Glama

Price Tables List

tiendanube_price_tables_list
Read-onlyIdempotent

List wholesale and B2B price tables with pagination, field selection, and JSON or markdown output to review available pricing lists.

Instructions

List price tables (wholesale / B2B price lists). HTTP: GET /products/price-tables Required scope: read_products API version: 2025-03 Returns {count, page, per_page, total?, has_more, next_page?, items[]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiendanube_price_tables_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)
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.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the concrete endpoint, required scope (read_products) and API version, plus the response envelope {count, page, per_page, total?, has_more, next_page?, items[]} — meaningful behavioral context, especially since no output schema exists.

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 purpose is front-loaded on the first line, followed by compact metadata lines. Every line carries information; the HTTP verb/path and API version are mildly redundant for an agent given the tool name but are cheap and useful for tracing.

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, the description usefully supplies the pagination envelope and count/has_more/next_page fields, and covers scope and version. For a zero-required-parameter list tool with fully documented params, that is nearly everything an agent needs to call it correctly.

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% and every parameter (page, per_page, fields, response_format) is documented in the schema, so the description does not need to compensate. It adds no parameter meaning beyond the schema, which is the baseline-3 case.

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+resource ('List price tables') and clarifies the domain with '(wholesale / B2B price lists)', which disambiguates it from unrelated list tools. It doesn't explicitly distinguish itself from adjacent siblings like price_tables_variants_list or price_tables_customers_list, relying on the name and endpoint path to imply top-level tables.

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 never says when to use this versus price_tables_get, price_tables_variants_list, or price_tables_customers_list, nor does it state prerequisites beyond the scope token. The B2B/wholesale parenthetical hints at the domain but stops short of routing guidance.

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