Example prompt: "List all my Contentful spaces"

2. Get Space Details

Retrieve detailed metadata for a specific space including its current sys.version, which is required for updates.

Tool: CONTENTFUL_GET_SPACE

Key parameters:

• space_id (required) -- the ID of the space to retrieve (alphanumeric, 1-64 chars)

Example prompt: "Get details for Contentful space abc123def"

3. Update Space Name

Update the name of a specific space. Requires the current version number for optimistic locking to prevent concurrent modification conflicts.

Tool: CONTENTFUL_UPDATE_SPACE

Key parameters:

• space_id (required) -- ID of the space to update
• name (required) -- new name for the space (1-255 chars)
• version (required) -- current space version from sys.version (must be > 0)

Example prompt: "Rename Contentful space abc123def to 'Production Content Hub'"

4. Audit Space Inventory

Combine space listing and detail retrieval to audit your organization's Contentful spaces.

Tools: CONTENTFUL_LIST_SPACES then CONTENTFUL_GET_SPACE

Workflow:

1. List all spaces to get IDs and names
2. Fetch details for each space to get version info, creation dates, and metadata

Example prompt: "Audit all Contentful spaces -- list them with their creation dates and current versions"

Known Pitfalls

• Version conflicts on update: CONTENTFUL_UPDATE_SPACE requires the latest sys.version from CONTENTFUL_GET_SPACE. If someone else modified the space between your read and write, the update will fail with a version conflict. Always fetch the space immediately before updating.
• Pagination for many spaces: CONTENTFUL_LIST_SPACES uses limit and skip parameters. When you have many spaces, iterate by incrementing skip until no more results are returned to avoid missing spaces.
• Scope limitations: These tools only manage space-level metadata (names). They cannot create or modify entries, content types, or assets within a space.
• Auth/permissions mismatch: Updates via CONTENTFUL_UPDATE_SPACE will fail if your token lacks space management scopes, even if reads via CONTENTFUL_GET_SPACE succeed. Verify your token has write permissions.
• Space ID format: The space_id must match the pattern ^[a-zA-Z0-9-_.]{1,64}$. Invalid characters will be rejected.

Quick Reference

Powered by Composio