Cactal

List websites

websites_list

Read-onlyIdempotent

Lists accessible websites. By default returns active websites: use organizationId to scope one organization, scope=shared without it for direct grants outside your memberships, or scope=all with it to combine both; supports sort by createdAt, updatedAt, or name and case-insensitive search, and each item includes organizationSlug, primaryHostname, and whether it is shared. Pass status=deleted with organizationId (requires organization-level trash access) to list restorable soft-deleted websites instead, each with its deletion time and purge deadline; deleted rows drop out when their 30-day restore window expires. Both modes use cursor pagination (default 20 per page, maximum 100). Fetch one website with websites.get.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "websites_list"
  }
}

Input Schema

Name	Required	Description
`sort`	No
`limit`	No
`scope`	No
`cursor`	No
`search`	No
`status`	No	Which websites to list. Defaults to `active`. `deleted` returns the organization’s restorable soft-deleted websites (requires `organizationId` and organization-level trash access) with their deletion time and purge deadline.
`organizationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that deleted results are restorable soft-deleted websites, include deletion time and purge deadline, and disappear after a 30-day restore window. It also documents pagination defaults and maximums, which are important behavioral details not covered by the annotations.

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 dense but front-loaded and every clause adds useful operational context for a seven-parameter tool with sparse schema descriptions. Despite its length, it avoids repetition and moves from default behavior to scoping, search/sort, deleted mode, and pagination.

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?

The definition is complete for an agent deciding whether and how to list websites: it covers defaults, scoping combinations, deleted-site access requirements, pagination, and representative item fields. No output schema exists, but the description gives enough return-shape context to set expectations without over-specifying.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description carries most of the parameter semantics and does so thoroughly. It explains how `organizationId`, `scope`, `sort`, `search`, `status`, cursor pagination, and `limit` interact, including enum-like usage and the precondition for deleted listings.

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 opens with a specific verb and resource: it lists accessible websites, with a clear active-by-default scope. It also distinguishes the tool from the closely related `websites.get` by directing single-item retrieval there.

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?

It explicitly explains default behavior and the alternative modes: `organizationId` for one organization, `scope=shared` without it for direct grants, and `scope=all` with it to combine both. It also states exactly when to use `status=deleted` and that it requires `organizationId` plus organization-level trash access.

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

All Cactal tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?