list_themesList all themes available to the account (own + shared)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | One row per theme — id, name, its complete tokens map, the cover_page and thank_you_page config, and whether it is the account default. | |
| meta | No | Page, limit and total row count. | |
| success | Yes | True when the call succeeded. |
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / properties / meta / descriptionPrevious value: -"Pagination for the list — page, limit and the total row count."New value: +"Page, limit and total row count."Output schema / properties / meta / properties / limit / descriptionPrevious value: -"Maximum rows per page."New value: +"Max rows per page."Output schema / properties / meta / properties / page / descriptionPrevious value: -"Zero-based index of the page returned."New value: +"Page index, zero-based."Output schema / properties / meta / properties / total / descriptionPrevious value: -"Total rows matching the query across all pages."New value: +"Total rows matching the query."Output schema / properties / success / descriptionPrevious value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "description": "One row per theme — id, name, its complete tokens map, the cover_page and thank_you_page config, and whether it is the account default.",
+ "items": {},
+ "type": "array"
+ },
+ "meta": {
+ "additionalProperties": true,
+ "description": "Pagination for the list — page, limit and the total row count.",
+ "properties": {
+ "limit": {
+ "description": "Maximum rows per page.",
+ "type": "number"
+ },
+ "page": {
+ "description": "Zero-based index of the page returned.",
+ "type": "number"
+ },
+ "total": {
+ "description": "Total rows matching the query across all pages.",
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds the ownership scoping detail 'own + shared', which is useful, but it does not disclose anything further such as auth needs, pagination, or result behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence communicates the operation, resource, and scope without filler. Every word contributes meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless read-only list operation with an output schema present, the description covers what is needed: the operation, the resource, and the scope. Nothing material is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters, the schema has nothing to document and the description is not required to explain parameters. The description still usefully clarifies the result scope, so the baseline 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List'), a concrete resource ('all themes available to the account'), and adds the important scope detail '(own + shared)'. This cleanly distinguishes it from singular get_theme and from other list_* siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The scope '(own + shared)' implies when this tool is appropriate, but there is no explicit guidance about when to prefer it over alternatives such as get_theme or list_assets. Usage context is clear enough for a straightforward list operation, but no exclusions or alternative routing are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.