Agility Cms Automation

What This Skill Does

• This skill automates Agility CMS operations using Composio's Agility CMS toolkit through Rube MCP
• It allows users to discover available tools, check connections, and execute tasks within the Agility CMS environment
• It is designed for developers and content managers who need to integrate Agility CMS functionalities into their workflows.

When to Use

• Discover available Agility CMS tools
• Check the status of an Agility CMS connection
• Execute specific Agility CMS tasks
• Automate content management tasks
• Integrate Agility CMS with other systems
• Troubleshoot Agility CMS connection issues.

Key Features

• Automates Agility CMS operations via Rube MCP
• Uses Composio's Agility CMS toolkit
• Discovers available tools using RUBE_SEARCH_TOOLS
• Manages connections using RUBE_MANAGE_CONNECTIONS
• Executes tools using RUBE_MULTI_EXECUTE_TOOL
• Provides a structured workflow pattern.

Agility CMS Automation via Rube MCP

Automate Agility CMS operations through Composio's Agility CMS toolkit via Rube MCP.

Toolkit docs: {toolkit}

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Agility CMS connection via RUBE_MANAGE_CONNECTIONS with toolkit agility_cms 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 agility_cms 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: "Agility CMS 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 Agility CMS task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["agility_cms"] 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

Powered by Composio