RevenueScope: revenue-first analytics for your EC site

List available sites

list_sites

Read-only

List the sites this signed-in account can analyze, in two groups. Each site includes its timezone and today's date in that timezone. Requires OAuth; no site registration is needed. Prefer my_sites; if site_id is omitted, analytics tools use the primary site. When my_sites is empty, analytics tools use the first curated demo site and identify it as sample data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`my_sites`	Yes
`demo_sites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / demo_sites / items / properties / today
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / demo_sites / items / required

Previous value: -[
-  "site_id",
-  "label",
-  "timezone",
-  "is_demo"
-]New value: +[
+  "site_id",
+  "label",
+  "timezone",
+  "today",
+  "is_demo"
+]

addedOutput schema / properties / my_sites / items / properties / today
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / my_sites / items / required

Previous value: -[
-  "site_id",
-  "name",
-  "domain",
-  "is_primary",
-  "created_at",
-  "timezone",
-  "is_demo"
-]New value: +[
+  "site_id",
+  "name",
+  "domain",
+  "is_primary",
+  "created_at",
+  "timezone",
+  "today",
+  "is_demo"
+]

Changed6 schema fields changedSep 27, 2026

addedOutput schema / properties / demo_sites / items / properties / is_demo
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / demo_sites / items / properties / timezone
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / demo_sites / items / required

Previous value: -[
-  "site_id",
-  "label"
-]New value: +[
+  "site_id",
+  "label",
+  "timezone",
+  "is_demo"
+]

addedOutput schema / properties / my_sites / items / properties / is_demo
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / my_sites / items / properties / timezone
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / my_sites / items / required

Previous value: -[
-  "site_id",
-  "name",
-  "domain",
-  "is_primary",
-  "created_at"
-]New value: +[
+  "site_id",
+  "name",
+  "domain",
+  "is_primary",
+  "created_at",
+  "timezone",
+  "is_demo"
+]

Changed1 schema field changedJun 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "demo_sites": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "site_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "site_id",
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "my_sites": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "domain": {
+            "type": "string"
+          },
+          "is_primary": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "site_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "site_id",
+          "name",
+          "domain",
+          "is_primary",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "my_sites",
+    "demo_sites",
+    "note"
+  ],
+  "type": "object"
+}

AddedJun 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses OAuth requirement, no registration needed, two grouping structure, per-site timezone/date, and fallback logic for analytics tools using primary or demo sample data. This is rich behavioral context that an agent needs to interpret results and site defaults.

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?

The description is front-loaded with the tool's core action, then adds necessary auth and downstream context in a few dense but purposeful sentences. There is no redundant or filler text.

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?

Given the output schema exists and annotations cover safety, the description still supplies the auth requirement, grouping, per-site metadata, and fallback behavior that an agent needs to use the tool correctly. Nothing essential is missing.

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 has zero input parameters, so the baseline is 4. The description mentions site_id only in relation to other analytics tools, not as a parameter of this tool, so there is no additional parameter semantics to add.

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 starts with a specific verb and resource ('List the sites this signed-in account can analyze, in two groups') and distinguishes the tool from analytics siblings by explaining their default site selection behavior. It leaves no ambiguity about what the tool returns.

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 names an alternative ('Prefer my_sites') and explains downstream defaults when site_id is omitted or my_sites is empty, which helps an agent understand when this tool is relevant. However, it does not explicitly state when not to use list_sites or what my_sites returns, so it falls short of full when/when-not guidance.

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

All RevenueScope: revenue-first analytics for your EC site 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?