Cactal

List or search assets

websiteAssets_list

Read-onlyIdempotent

Returns ready assets newest first as compact rows (description, category, dimensions, url, srcSet); fetch one asset for originalUrl and variants. Filter by kind, category, type (the broad MIME family: image, video, audio, font, or document), or search, which prefix-matches each term against the filename, description, and category; every term must match, else any term. Page size defaults to 50 (max 100).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "websiteId": "<websiteId>"
    },
    "name": "websiteAssets_list"
  }
}

Input Schema

Name	Required	Description
`kind`	No
`type`	No	Broad file type derived from the MIME type: image, video, audio, font, or document (everything else). Combines with kind, category, and search.
`limit`	No
`cursor`	No
`search`	No	Matches filename, description, and category; each term matches as a prefix.
`category`	No	Only images with this category.
`websiteId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description's job is to add beyond that — and it does: rows are 'compact' (reduced payload), sorted newest first, capped at 100 per page. It omits cursor/pagination continuation behavior, which is the main remaining gap.

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

Conciseness4/5

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

Single dense sentence that front-loads the return shape and then the filters — no filler. It is packed with parentheticals and semicolon clauses, which costs a bit of scannability but every clause carries information.

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?

With no output schema, the description helpfully enumerates returned fields and notes the compact-vs-full split across two tools. Missing pieces are cursor-based paging and how `kind` relates to the overlapping `type` enum, which an agent could easily conflate.

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?

At 43% schema coverage the description must compensate, and it does for most: it explains `type` as the MIME family, `search` as per-term prefix matching against filename/description/category, and `limit`'s default and cap. `kind` and `cursor` remain undocumented, and the kind-vs-type overlap is not clarified.

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+resource ('Returns ready assets') plus ordering ('newest first') and return shape, and explicitly routes the single-asset case to a separate fetch, distinguishing it from websiteAssets_get. An agent knows immediately this is the collection-listing endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly signals when to use this tool versus the single-asset variant ('fetch one asset for originalUrl and variants'), and enumerates the available filter axes. It doesn't state exclusions (e.g. that update/delete need IDs from here) but the context is unambiguous.

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?