What is Textrazor automation via Rube MCP?

It automates Textrazor operations through Composio's Textrazor toolkit managed by the Rube MCP integration.

Do I always need to search tools before running?

Yes. The workflow requires RUBE_SEARCH_TOOLS to fetch current tool schemas and avoid hardcoding.

What if the connection shows NOT ACTIVE?

Follow the auth flow in RUBE_MANAGE_CONNECTIONS to activate the Textrazor toolkit, then re-check status.

textrazor-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Textrazor Automation via Rube MCP

Automate Textrazor operations through Composio's Textrazor toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/textrazor

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["textrazor"]
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 Textrazor-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor`
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/textrazor-automation/SKILL.mdView on GitHub

Overview

Automate Textrazor tasks through Composio's Textrazor toolkit using Rube MCP. Always search tools first to fetch current schemas and avoid hardcoding. This keeps workflows aligned with updated tool slugs, inputs, and pitfalls.

How This Skill Works

The workflow discovers available Textrazor tools via RUBE_SEARCH_TOOLS, then verifies an ACTIVE Textrazor connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the proper memory payload. Tool schemas from the search results drive exact field names and types for execution.

When to Use It

You need to automate multiple Textrazor operations across documents using a single session.
Tool schemas change frequently and you want to avoid hardcoding slugs or arguments.
You must ensure the Textrazor connection is ACTIVE before running workflows.
You want to resume work mid-workflow by reusing a session_id.
You aim to orchestrate bulk Textrazor tasks or parallel executions via bulk tools.

Quick Start

Step 1: Add the Rube MCP endpoint https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect to the textrazor toolkit with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool using RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always search first with RUBE_SEARCH_TOOLS to obtain current tool schemas.
Check the connection status with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE.
Use exact field names and types from the search results; do not guess schemas.
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and manage pagination tokens when present.

Example Use Cases

Automate a batch of entity extraction tasks across documents by chaining Textrazor tools with a single session.
Validate updated Textrazor tool schemas by discovering tools first before implementing a new workflow.
Execute multiple Textrazor analyses in parallel using RUBE_MULTI_EXECUTE_TOOL and memory payloads.
Resume a paused Textrazor workflow by reusing a session_id and rechecking ACTIVE connection.
Coordinate Textrazor tasks alongside other Composio tools via RUBE_REMOTE_WORKBENCH for bulk processing.

Frequently Asked Questions

Add this skill to your agents