home / skills / composiohq / awesome-claude-skills / pdf-api-io-automation

pdf-api-io-automation skill

safe

/pdf-api-io-automation

This skill automates PDF API IO tasks using the Composio toolkit via Rube MCP, ensuring current tool schemas are discovered first.

npx playbooks add skill composiohq/awesome-claude-skills --skill pdf-api-io-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: pdf-api-io-automation
description: "Automate PDF API IO tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# PDF API IO Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/pdf_api_io](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_api_io`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with PDF API IO-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_api_io` |
| 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](https://composio.dev)*

Overview

This skill automates PDF API IO tasks using Composio's toolkit via Rube MCP (Composio). It guides discovery of available tools, ensures active connections, and runs schema-compliant executions to manipulate PDFs reliably. The workflow emphasizes searching tools first and maintaining session and memory discipline to avoid runtime errors.

How this skill works

First, call RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended plans. Next, verify or establish an active PDF API IO connection with RUBE_MANAGE_CONNECTIONS. Finally, run operations through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) using the exact arguments returned by the search schema and include a memory object and consistent session_id.

When to use it

Automating PDF creation, merging, splitting, or metadata updates via Composio toolkit.
Batch-processing many PDFs using remote workbench or multi-execute strategies.
Embedding PDF operations inside larger Claude agent workflows that require external tool calls.
When tool schemas are expected to change frequently and dynamic discovery is required.
Running workflows that must preserve session state and pagination across calls.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit pdf_api_io before executing.
Pass memory (even empty {}) in RUBE_MULTI_EXECUTE_TOOL and reuse session_id within a workflow.
Use RUBE_GET_TOOL_SCHEMAS or the search results schemaRef for exact field names and types.
Handle pagination tokens and iterate until responses are complete.

Example use cases

Search available PDF tools then merge a list of documents using the discovered merge tool and schema.
Connect to pdf_api_io, run bulk redaction or OCR tasks through RUBE_REMOTE_WORKBENCH, and monitor job results.
Automate metadata extraction across a document corpus by retrieving schema fields and running repeated multi-execute calls.
Create a workflow that splits large PDFs into pages, stores results, and updates an index with pagination handling.

FAQ

What is the first call I should make every time?

Always call RUBE_SEARCH_TOOLS to get current tool slugs and input schemas before doing anything else.

What if the connection is not active?

Call RUBE_MANAGE_CONNECTIONS for toolkit pdf_api_io and follow the provided auth link to activate the connection, then confirm ACTIVE status.