Skip to main content
Glama
kuklaph
by kuklaph

List Cascade Sites

cascade_list_sites
Read-onlyIdempotent

List all sites accessible with current API credentials, returning identifiers (id, name, type) for each site to enable discovery before reading or editing assets.

Instructions

List all sites accessible with the current API credentials.

Returns identifiers (id, name, type="site") for every site the authenticated user can see. This is typically the first call an agent makes to discover which sites exist before reading or editing assets inside them. The response contains only identifiers — call cascade_read with { type: "site", ... } to fetch a site's full configuration.

Args: (none)

Returns: Cascade OperationResult: { success: true, sites: [ { id, type: "site", path: { path, siteId, siteName } }, ... ] } On failure: { success: false, message: "" }

Examples:

  • Use when: "What sites do I have access to?" -> {}

  • Use when: "I need to find a siteId before reading a page" -> call this, then match by name.

  • Don't use when: You already know the site name/id — skip straight to cascade_read.

  • Don't use when: You need a site's full config — use cascade_read with type "site".

Error Handling:

  • "Permission denied" when credentials are invalid

  • "Authentication failed" when the API key is missing or revoked. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent, and open world. The description adds useful context about return structure (identifiers only) and error handling scenarios, but no additional behavioral traits beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections (args, returns, examples, error handling) but overly verbose with generic boilerplate about responses and _cache metadata that is not specific to this tool. Could be trimmed.

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 no parameters, no output schema, and strong annotations, the description covers purpose, typical usage, return structure, and error handling. It is complete for an agent to use effectively.

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?

No parameters exist; baseline is 4. The description correctly notes '(none)' args, so no added meaning needed beyond 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?

The description clearly states the tool lists all sites accessible with current credentials and returns identifiers. It distinguishes itself from sibling tools like cascade_read by specifying it only returns basic info, not full configuration.

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?

Explicitly states when to use (first call to discover sites) and when not to (already know site name/id, need full config). Includes examples of natural language queries that map to this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuklaph/cascade-cms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server