AirShelf Catalog

List merchants

list_merchants

Read-only

List public AirShelf merchants that have an assigned slug and at least one active product. Every listed merchant has an account with AirShelf; catalog makers without one are not listed. Internal/demo and empty catalogs are excluded. Returns each merchant's name, slug, and product count; the slug is the merchant argument for request_quote.

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": "list_merchants"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`total`	No
`merchants`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

addedOutput schema / properties / merchants / items / properties / checkout_capability

Added value: +{
+  "description": "shopify indicates a connected Shopify store; redirect sends the buyer to the product page.",
+  "enum": [
+    "shopify",
+    "redirect"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / merchants / items / properties / manifest_url

Added value: +{
+  "description": "Merchant agent manifest URL with supported endpoints and capabilities.",
+  "type": "string"
+}

addedOutput schema / properties / merchants / items / properties / products_url

Added value: +{
+  "description": "Merchant product-listing endpoint URL.",
+  "type": "string"
+}

addedOutput schema / properties / merchants / items / properties / search_url

Added value: +{
+  "description": "Merchant-scoped product-search endpoint URL.",
+  "type": "string"
+}

Changed4 schema fields changedAug 5, 2026
- addedOutput schema / properties / merchants / items / properties / product_count / exclusiveMinimum
```
Added value: +0
```
- removedOutput schema / properties / merchants / items / properties / slug / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / merchants / items / properties / slug / type
```
Added value: +"string"
```
- changedOutput schema / properties / merchants / items / required
```
Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "slug",
+  "product_count"
+]
```

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "merchants": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "domain": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "product_count": {
+            "type": "number"
+          },
+          "slug": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "merchants"
+  ],
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The readOnly and non-destructive annotations already make the safety profile clear. Beyond them, the description discloses the exclusion rules that matter for interpreting results: no internal/demo catalogs, no empty catalogs, and no catalog makers lacking an AirShelf account. It says nothing about pagination or ordering, but in all other respects it is richer than the annotations.

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?

Four short sentences, and the sentence that states the tool's core scope comes first. The sentence about the return fields and the sentence about the request_quote link each carry distinct information, so nothing is wasted.

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?

An output schema exists, so field-level return documentation is not required. The description still fills the remaining gaps: which merchants appear in that schema, which are filtered out, and how a returned slug is consumed by a sibling tool, so an agent has everything it needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and there is nothing to document. The description correctly imposes no argument burden on the caller and instead documents the one output field that is an input elsewhere (slug feeding request_quote).

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?

The description gives a specific verb and resource ('List public AirShelf merchants') plus the exact inclusion criteria: assigned slug and at least one active product. This is enough to separate it from every sibling, all of which operate on products or quotes rather than merchants.

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

Usage Guidelines4/5

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

It states the downstream use case clearly: 'the slug is the `merchant` argument for request_quote', which tells an agent when this tool is the right first step. It does not name an alternative or an explicit case where this tool should be avoided, but no sibling lists merchants, so there is nothing to route against.

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

All AirShelf Catalog 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.

Resources

Need Help?