Canopy API

Get GTIN from ASIN

get_amazon_gtin_from_asin

Read-only

Look up the GTIN (ISBN, UPC or EAN code) for an Amazon product by its ASIN.

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": {
      "asin": "<asin>"
    },
    "name": "get_amazon_gtin_from_asin"
  }
}

Input Schema

Name	Required	Description	Default
`asin`	Yes	The ASIN for a product (e.g. B01HY0JA3G)
`domain`	No	The domain for fetching product data, defaults to US	US

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026
- removedOutput schema / properties / data / properties / amazonProduct / properties / gtin / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / amazonProduct / properties / gtin / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful semantic detail that GTIN means ISBN/UPC/EAN, but says nothing about failure cases (products with no GTIN), rate limits, or regional data availability beyond what the domain param implies.

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?

A single front-loaded sentence with the verb, the returned identifier type, and the input key named. No filler and nothing important buried.

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?

An output schema exists, so return values need not be explained, and the tool has only two fully documented parameters. What remains missing is minor: whether every ASIN resolves to a GTIN and how a missing GTIN is surfaced.

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%: the ASIN format example and the domain enum with its US default are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, 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 ('look up the GTIN ... for an Amazon product by its ASIN') and expands the acronym so the agent knows exactly what value comes back. The direction of the conversion is unambiguous against the inverse sibling get_amazon_asin_from_gtin, though that sibling is never named.

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 input/output direction: supply an ASIN when a GTIN is needed. There is no explicit statement of when to prefer this over alternatives (e.g. get_amazon_product, which may also expose identifiers) and no note about products that lack a GTIN.

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

All Canopy API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.