Contentful Automation

---
name: Contentful Automation
description: "Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration."
requires:
  mcp:
    - rube
executor: HYBRID
skill_id: integrations.composio.contentful-automation
status: ADOPTED
security: {level: standard, pii: false, approval_required: false}
extends: integrations.composio.meta
toolkit: contentful-automation
# Phase3: This stub routes to the meta-skill. See skills/integrations/composio/SKILL.md for full protocol.
anchors:
  - automation
  - integration
  - api
  - workflow
tier: 3
input_schema:
  - name: code_or_task
    type: string
    description: "Code snippet, script, or task description to process"
    required: true
output_schema:
  - name: result
    type: object
    description: "Result from the automated action"
  - name: status
    type: string
    description: "Execution status: success | partial | failure"
what_if_fails: >
  FALLBACK: If Contentful cannot complete, provide partial results with
  explicit gaps noted. Never block workflow silently.
  ESCALATE: If core capability is unavailable, suggest nearest alternative skill.
  RULE: Always explain what failed and what manual steps can substitute.
---

# Contentful Automation

Manage your **Contentful** headless CMS spaces directly from Claude Code. List spaces, retrieve metadata, and update space configurations without leaving your terminal.

**Toolkit docs:** [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful)

---

## Setup

1. Add the Composio MCP server to your configuration:
   ```
   https://rube.app/mcp
   ```
2. Connect your Contentful account when prompted. The agent will provide an authentication link. Ensure your access token has space management scopes.

---

## Core Workflows

### 1. List All Spaces

Discover all Contentful spaces accessible to your authenticated account. This is typically the first operation since most other actions require a `space_id`.

**Tool:** `CONTENTFUL_LIST_SPACES`

Key parameters:
- `limit` (1-1000) -- maximum number of spaces to return (default: 100)
- `skip` -- number of spaces to skip for pagination
- `order` -- sort by field, e.g., `sys.createdAt` or `-sys.createdAt` for descending

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

| Tool Slug | Description |
|---|---|
| `CONTENTFUL_LIST_SPACES` | List all spaces accessible to your account |
| `CONTENTFUL_GET_SPACE` | Retrieve detailed metadata for a single space |
| `CONTENTFUL_UPDATE_SPACE` | Update the name of a space (requires version) |

---

*Powered by [Composio](https://composio.dev)*

## Why This Skill Exists
Stub for the `contentful-automation` toolkit in the Composio integration ecosystem.
Extends `integrations.composio.meta` — see the meta-skill for full protocol.

## When to Use
Use when automating `contentful-automation` tasks via Rube MCP (Composio).
For generic Composio queries, use `integrations.composio.meta` directly.

## What If Fails
See `skills/integrations/composio/SKILL.md` (meta-skill) for full fallback protocol.
RULE: Never block workflow — always suggest manual alternative if automation fails.