Tanatasa Beauty

list_orders

Read-onlyIdempotent

List the signed-in customer's paid orders, newest first, from the website or any assistant: status, total, items, tracking and change requests. Needs account_token from sign_in (or an account-linked connection). Follow next_page for older orders.

Input Schema

Name	Required	Description
`page`	No	Page; use next_page from the previous result.
`limit`	No	Orders per page (default 10, up to 50).
`guest_token`	No	Private guest session token from create_cart. Retain for cart, checkout and purchase-status calls; no account login needed.
`account_token`	No	Private account token from sign_in, after the customer gave you the code from their email. Lets quotes and checkout use their cashback credit, and opens their orders.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -{
-  "anyOf": [
-    {
-      "$schema": "http://json-schema.org/draft-07/schema#",
-      "additionalProperties": true,
-      "properties": {
-        "email": {
-          "type": "string"
-        },
-        "next_page": {
-          "anyOf": [
-            {
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "note": {
-          "type": "string"
-        },
-        "orders": {
-          "items": {
-            "additionalProperties": true,
-            "properties": {
-              "currency": {
-                "const": "SGD",
-                "type": "string"
-              },
-              "money_unit": {
-                "const": "cents",
-                "type": "string"
-              },
-              "order_id": {
-                "type": "string"
-              },
-              "status": {
-                "type": "string"
-              },
-              "total": {
-                "description": "Integer SGD cents; 1690 means S$16.90.",
-                "minimum": 0,
-                "type": "integer"
-              }
-            },
-            "required": [
-              "currency",
-              "money_unit",
-              "order_id",
-              "status",
-              "total"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "page": {
-          "type": "integer"
-        }
-      },
-      "required": [
-        "email",
-        "orders",
-        "page",
-        "next_page",
-        "note"
-      ],
-      "type": "object"
-    },
-    {
-      "additionalProperties": true,
-      "properties": {
-        "error": {
-          "additionalProperties": true,
-          "properties": {
-            "code": {
-              "type": "string"
-            },
-            "message": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "code",
-            "message"
-          ],
-          "type": "object"
-        }
-      },
-      "required": [
-        "error"
-      ],
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "$schema": "http://json-schema.org/draft-07/schema#",
+      "additionalProperties": true,
+      "properties": {
+        "email": {
+          "type": "string"
+        },
+        "next_page": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "note": {
+          "type": "string"
+        },
+        "orders": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "currency": {
+                "const": "SGD",
+                "type": "string"
+              },
+              "money_unit": {
+                "const": "cents",
+                "type": "string"
+              },
+              "order_id": {
+                "type": "string"
+              },
+              "status": {
+                "type": "string"
+              },
+              "total": {
+                "description": "Integer SGD cents; 1690 means S$16.90.",
+                "minimum": 0,
+                "type": "integer"
+              }
+            },
+            "required": [
+              "currency",
+              "money_unit",
+              "order_id",
+              "status",
+              "total"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "page": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "email",
+        "orders",
+        "page",
+        "next_page",
+        "note"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "error": {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

AddedOct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is fully covered. The description usefully adds ordering (newest first), the returned fields (status, total, items, tracking, change requests) and the auth requirement, but adds little else about rate limits or error behavior.

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?

Two dense sentences with the core operation front-loaded and no redundancy. The clause 'from the website or any assistant' is mildly vague filler, keeping it off a 5.

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?

No output schema exists, so the description compensates by enumerating the returned fields, and it covers auth and pagination. A reader still has to infer whether guest sessions can call it, a small remaining gap.

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 all four parameters are already documented, including the guest_token/account_token distinction. The description only echoes the account_token prerequisite and the next_page mechanic, so 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 ('List the signed-in customer's paid orders') with scope ('newest first') and the fields returned. It never names a sibling such as get_order for single-order lookup, so it stops short of full sibling differentiation.

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?

Gives a clear prerequisite ('Needs account_token from sign_in (or an account-linked connection)') and pagination direction ('Follow next_page for older orders'). It doesn't state when to prefer get_order or whether guest_token alone is valid here, so no exclusions are covered.

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

All Tanatasa Beauty 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?