WebTwizz

Templates

list-templates

Read-only

Use this when the user wants to start from a ready-made design, or asks what WebTwizz templates there are. Shows matching templates with a picture and a live demo, a page at a time; show-template opens one, and its slug goes to create-site as template. Works before the user signs in.

Input Schema

Name	Required	Description
`page`	No	Which page of templates, 1 by default
`search`	No	Words about the kind of site, like bakery, portfolio or saas
`category`	No

Output Schema

Name	Required	Description	Default
`more`	Yes
`note`	No
`page`	Yes
`view`	Yes
`search`	No
`category`	No
`signed_in`	Yes
`templates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 26, 2026

addedInput schema / properties / page

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

addedOutput schema / properties / category

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

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 / signed_in
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / view
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "templates"
-]New value: +[
+  "view",
+  "signed_in",
+  "page",
+  "more",
+  "templates"
+]

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so safety is covered; the description adds genuinely new context with 'Works before the user signs in' (no auth prerequisite) and 'a page at a time' (pagination behavior). Return format is left to the output schema, which exists.

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?

Two tight sentences, front-loaded with the usage trigger, then the alternatives and the auth caveat. No filler.

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?

For a read-only paginated list with an output schema, an agent has everything it needs to invoke correctly, including the pre-sign-in caveat. The one gap is what the category values mean, which is minor given the enum is self-descriptive.

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 coverage is 67% and page/search are already documented; the description only reinforces pagination with 'a page at a time'. The category enum (websites/apps/games) is left unexplained in both schema and description, so no value is added beyond structured fields.

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 (shows matching templates) and resource, plus what the caller receives (picture and live demo, paginated). It explicitly distinguishes itself from show-template and create-site, so an agent can route between the three.

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 an explicit trigger ('when the user wants to start from a ready-made design, or asks what WebTwizz templates there are') and names the follow-on alternatives: show-template to open one, its slug to create-site. Nothing is left to inference.

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?