Skip to main content
Glama

import_size_measurements

Read-only

Get the blank's real per-size measurements from its fulfillment provider, in the exact shape size_chart_measurements takes. READ-ONLY. Use this instead of asking a merchant to type a size chart, and never instead of asking them when it comes back unavailable.

It imports nothing by itself — adopting a set of measurements is the merchant's decision. Show them the table, let them correct it, then write it back with set_listing_attributes as size_chart_measurements.

available: false is an ANSWER, not a failure. Branch on reason: • provider_publishes_no_size_guide — this provider has no size-guide API at all (Printify and Gelato), so no product of theirs will ever import. Permanent: ask the merchant for the blank manufacturer's own numbers. • no_size_guide_for_this_blank — the provider does publish guides, just not for this item. Normal for non-apparel. • provider_lookup_unavailable — transient. Retry. • product_has_no_fulfillment_provider — nothing to import from.

⚠️ TELL THE MERCHANT WHERE THE NUMBERS CAME FROM. source names the provider and the catalog item. These are measurements a buyer makes a purchase decision on, published in the merchant's name — present them as the provider's figures for a specific blank, not as something you know.

notes, when present, lists what was adjusted on the way through (a provider sometimes files a measurement under a size outside its own size list). Pass those on rather than dropping them.

[#19618b]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNo
store_uuidYes
product_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description reinforces 'READ-ONLY'. Beyond that it discloses the failure envelope (`available: false` is an answer, not a failure) and enumerates four `reason` values with permanence/retry semantics, plus the source-attribution and `notes` caveats. This is behavioral context the schema and annotations cannot carry.

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?

Front-loaded with purpose and the READ-ONLY flag, then usage, then a bulleted error taxonomy. Long, but each block earns its place; the error bullets are dense rather than redundant. The trailing issue tag is inert noise.

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

Completeness5/5

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

No output schema exists, and the description effectively supplies one by describing the return envelope: `available`, `reason`, `source`, and `notes`, with the meaning of each. Combined with the read-only profile and the handoff to set_listing_attributes, an agent has everything needed to call and interpret it.

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 0% and the description never explains store_uuid, product_uuid, or workspace. It implies the lookup hinges on a product/blank and its provider, but an agent gets no statement of which identifier scopes what or whether workspace is required. With three undocumented parameters this is a real gap.

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 ('Get the blank's real per-size measurements from its fulfillment provider') plus the shape guarantee ('in the exact shape `size_chart_measurements` takes'). It also implicitly separates itself from the write path (`set_listing_attributes`) that a confused agent might reach for.

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

Usage Guidelines5/5

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

Explicit when-to-use ('use this instead of asking a merchant to type a size chart') and when-not ('never instead of asking them when it comes back unavailable'), plus the downstream workflow (show table, let merchant correct, write back via set_listing_attributes). The 'it imports nothing by itself' clause pre-empts the most likely misinvocation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources