What is parsera-automation?

A method to automate Parsera operations via Composio's Parsera toolkit using Rube MCP, with a focus on always using current tool schemas.

Do I need API keys to use this skill?

No API keys are required. You should add the MCP server endpoint (e.g., https://rube.app/mcp) in your client configuration.

How do I handle changing tool schemas?

Always call RUBE_SEARCH_TOOLS before executing any tool to refresh slugs and input schemas, and avoid hardcoding tool slugs or arguments.

parsera-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Parsera Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/parsera

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Parsera operations using Composio's Parsera toolkit through Rube MCP. Always search for current tool schemas before running workflows, ensuring inputs stay up to date. This guide covers setup, discovery, execution, and best practices for reliable automation.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS is available. Always search for tool schemas first, then pick a tool slug and execute with RUBE_MULTI_EXECUTE_TOOL, including a memory object. Maintain an ACTIVE connection and reuse session IDs to streamline multi-tool workflows.

When to Use It

Automating Parsera tasks where tool schemas frequently change and slugs must be discovered at runtime
Running end-to-end Parsera workflows that require current schemas before each run
Onboarding new Parsera tasks that need up-to-date input schemas
Performing multi-step Parsera workflows that benefit from session reuse
Validating and re-establishing connections before executing Parsera tools

Quick Start

Step 1: Ensure Rube MCP is configured (add https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Run RUBE_SEARCH_TOOLS with a Parsera use_case to discover available tools and select a slug
Step 3: Execute the tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered arguments, a memory object, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Parsera tool to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the discovered tool schemas; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Example 1: Discover tools for a specific Parsera task, connect via RUBE_MANAGE_CONNECTIONS, then execute the chosen tool slug with proper arguments and a memory payload
Example 2: After a schema update, run RUBE_SEARCH_TOOLS to refresh inputs, adjust your arguments, and re-run the tool
Example 3: Execute a sequence of Parsera tools by reusing a single session_id across steps for faster automation
Example 4: Use RUBE_REMOTE_WORKBENCH to run multiple Parsera tools in a bulk operation with run_composio_tool()
Example 5: Detect a failed search or inactive connection, refresh schemas, re-establish the connection, and retry the workflow

Frequently Asked Questions

Add this skill to your agents