WebTwizz

Your sites

list-sites

Read-only

Use this when the user asks which WebTwizz sites they have, or wants to pick one to work on. Shows their most recently updated sites with a picture of each, newest first, a page at a time; search narrows them by name. When the user names a site they want to see, use show-preview with its name instead.

Input Schema

Name	Required	Description
`page`	No	Which page of sites, 1 by default
`search`	No	Only sites whose name contains this
`workspace_id`	No	Only sites in this workspace, from get-account. Leave out for all of them.

Output Schema

Name	Required	Description	Default
`more`	Yes
`page`	Yes
`view`	Yes
`sites`	Yes
`total`	Yes
`search`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 26, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "Which page of sites, 1 by default",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Only sites whose name contains this",
+  "type": "string"
+}

addedOutput schema / properties / more
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / page
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / search

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sites / items / properties / image_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / total
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / view
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "sites"
-]New value: +[
+  "view",
+  "sites",
+  "page",
+  "total",
+  "more"
+]

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds useful behavioral detail beyond them: results are most recently updated, include a picture, sorted newest first, returned a page at a time, and searchable by site name. That is substantial transparency for a list tool.

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?

Three sentences, front-loaded with usage and followed by return behavior and the sibling alternative. There is no noticeable filler, and each sentence contributes useful information.

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?

Annotations cover the safety profile, the schema fully documents parameters, and an output schema exists, so the description does not need to explain return values in depth. It still adds enough context about ordering, pagination, and filtering to call the tool correctly.

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 the baseline is 3. The description adds some meaning for pagination and search (“a page at a time”; “search narrows them by name”), but it does not mention workspace_id, leaving that parameter entirely to the schema.

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 (“list-sites” for the user’s WebTwizz sites) and clearly distinguishes it from the sibling show-preview when the user names a specific site. An agent can identify the tool’s role without opening the schema.

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?

Gives explicit when-to-use guidance (“when the user asks which WebTwizz sites they have, or wants to pick one to work on”) and an explicit alternative (“use show-preview with its name instead”) for a named site. This is strong routing guidance.

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

All WebTwizz 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?