Rube MCP is Composio's middleware that orchestrates Contentful GraphQL tasks by discovering, connecting, and executing tools through a centralized control plane.

Why must I run RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Running RUBE_SEARCH_TOOLS fetches the current tool slugs and required arguments, preventing hard-coded errors.

What if a tool's schema changes during a workflow?

Re-run RUBE_SEARCH_TOOLS to obtain updated inputs and adjust your execution accordingly. Always confirm the connection remains ACTIVE before continuing.

contentful-graphql-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/contentful-graphql-automation --openclaw

Files (1)

SKILL.md

3.0 KB

Contentful Graphql Automation via Rube MCP

Automate Contentful Graphql operations through Composio's Contentful Graphql toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/contentful_graphql

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Contentful Graphql connection via RUBE_MANAGE_CONNECTIONS with toolkit contentful_graphql
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit contentful_graphql
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Contentful Graphql operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Contentful Graphql task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["contentful_graphql"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Contentful Graphql-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `contentful_graphql`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/contentful-graphql-automation/SKILL.md

View on GitHub

Overview

Automates Contentful GraphQL operations using Composio's contentful_graphql toolkit via Rube MCP. It streamlines discovering current tool schemas, validating connections, and executing predefined tool workflows.

How This Skill Works

Begin by discovering available tools with RUBE_SEARCH_TOOLS to pull the current input schemas. Next, verify the contentful_graphql connection with RUBE_MANAGE_CONNECTIONS, ensuring the status is ACTIVE. Finally, execute the discovered tool using RUBE_MULTI_EXECUTE_TOOL, supplying exact arguments from the schema and including memory in every call.

When to Use It

When you need to automate recurring Contentful GraphQL queries or mutations.
When tool schemas change and you must pull current tool slugs and arguments before executing.
When you need to validate or re-establish a Contentful GraphQL connection before workflows.
When performing batch or bulk Contentful operations via discovered tools.
When reusing a workflow session to improve efficiency and maintain state.

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Contentful Graphql operations", known_fields: ""}] session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["contentful_graphql"] session_id: "your_session_id"
Step 3: RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */} }] memory: {} session_id: "your_session_id"

Best Practices

Always run RUBE_SEARCH_TOOLS before executing tools to get the latest schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tool.
Use exact field names and types as returned in the tool schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and handle pagination or continued results as needed

Example Use Cases

Weekly: fetch Contentful entries and update a downstream data store using discovered tool slugs.
Daily: export content types and entries for reporting via a mapped Contentful GraphQL operation.
Migration: verify and migrate entries between environments with schema-aligned inputs.
Campaigns: bulk publish/unpublish Contentful entries through automated tool executions.
Validation: run a quick schema check after Contentful schema changes to ensure compatibility.

Frequently Asked Questions

Add this skill to your agents