Skip to main content
Glama

Shipping Carriers List

tiendanube_shipping_carriers_list
Read-onlyIdempotent

Lists shipping carriers registered by the app, with pagination and field selection, to retrieve carrier data for shipping workflows.

Instructions

List shipping carriers registered by the app. HTTP: GET /shipping_carriers Required scope: read_shipping 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_shipping_carriers_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

A4/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, so the safety profile is covered. The description adds genuinely non-redundant context: the required OAuth scope 'read_shipping', the pinned API version 2025-03, and the pagination envelope returned. It stops short of mentioning rate limits or ordering of results.

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?

Five short, front-loaded lines: purpose first, then endpoint, scope, version, and return shape. No sentence is redundant, and the structured labels (HTTP:, Required scope:, API version:) make scanning fast.

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 compensates by spelling out the response envelope ({count, page, per_page, has_more, items[]}), and it discloses auth scope and API version. What remains absent is any indication of what fields a carrier item contains, which would matter when an agent decides on the 'fields' parameter.

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 page, per_page, fields and response_format are already documented with defaults and bounds. The description contributes nothing parameter-specific beyond naming the returned envelope fields, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List shipping carriers') and adds a meaningful scope qualifier ('registered by the app') that clarifies what is returned. It is trivially distinguishable from siblings like tiendanube_shipping_carriers_get, _create, _update and _delete by the list verb.

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?

The description implies usage (read_shipping scope, paginated listing) but never says when to prefer this over tiendanube_shipping_carriers_get or how to page through results. An agent must infer the selection criteria from the tool names alone.

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