Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.
getCMSCollectionsTOOL
Gets all CMS collections in the project with their field definitions.
IMPORTANT: Call this tool FIRST before using any other CMS tools to understand the field structure and get proper field IDs.
Returns collections with:
  • ID, name, and management status (user-managed or plugin-managed)
  • Field definitions with field IDs, names, types, and requirements
  • Field types include: string, number, boolean, color, date, image, link, formattedText, file, enum, collectionReference, multiCollectionReference
Each field includes:
  • id: The field identifier (e.g., "j11rZL4rT") - use this as the key in fieldData
  • name: Human-readable field name
  • type: The data type for this field
  • required: Whether the field is mandatory (when applicable)
  • allowedFileTypes: Array of allowed file extensions for file fields (e.g., ["pdf", "txt"])
  • cases: Array of enum options with id and name for enum fields
  • collectionId: Referenced collection ID for reference fields
  • Additional legacy properties like options, defaultValue, multiline when applicable
To create a new CMS collection, use the createCMSCollection tool.
You cannot update or add fields to existing user-managed collections, ask the user to do so. For plugin-managed collections created via createCMSCollection, you can set fields during creation.
read-only
Request example
{
  "method": "tools/call",
  "params": {
    "name": "getCMSCollections",
    "arguments": {}
  }
}
Powered byHolocron