Pdf API Io Automation

What This Skill Does

This skill automates PDF API IO operations using the Composio PDF API IO toolkit via Rube MCP. It is designed for users who need to programmatically interact with PDF files, such as creating, editing, and converting them. The skill streamlines workflows by providing tools to discover, connect, and execute PDF API IO tasks.

When to Use

• Automate PDF creation from templates.
• Convert documents to PDF format.
• Extract text from PDF files.
• Merge multiple PDF documents.
• Add watermarks to PDFs.
• Secure PDFs with passwords.

Key Features

• Automates PDF API IO tasks via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Requires active PDF API IO connection.
• Provides access to Composio's PDF API IO toolkit.

Manual Installation

Automate PDF API IO operations through Composio's PDF API IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/pdf_api_io

Prerequisites

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

Step 2: Check Connection

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

Automate PDF API IO operations through Composio's PDF API IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/pdf_api_io

Prerequisites

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

Step 2: Check Connection

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

Claude CodeCursorCodexGemini CLIAiderWindsurfOpenClaw

apiautomationdocumentsengineeringmcpproductivitysearch