API Ninjas Automation
This skill automates API Ninjas operations using Composio's API Ninjas toolkit through Rube MCP.
Install
npx promptshop add api-ninjas-automationDetails
What This Skill Does
This skill automates API Ninjas operations using Composio's API Ninjas toolkit through Rube MCP. It is designed for developers who need to integrate API Ninjas functionalities into their workflows. The skill ensures proper setup, tool discovery, and execution while adhering to schema compliance.
When to Use
- Automate API Ninjas tasks.
- Discover available API tools.
- Check API Ninjas connection status.
- Execute specific API Ninjas tools.
- Handle schema-compliant arguments.
- Integrate API Ninjas into workflows.
Key Features
- Uses Rube MCP for API Ninjas automation.
- Requires an active API Ninjas connection.
- Employs RUBE_SEARCH_TOOLS for tool discovery.
- Utilizes RUBE_MANAGE_CONNECTIONS for connection checks.
- Executes tools via RUBE_MULTI_EXECUTE_TOOL.
- Ensures schema compliance with API Ninjas.
Manual Installation
API Ninjas Automation via Rube MCP
Automate API Ninjas operations through Composio's API Ninjas toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/api_ninjas
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active API Ninjas connection via RUBE_MANAGE_CONNECTIONS with toolkit api_ninjas 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 api_ninjas 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: "API Ninjas 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 API Ninjas task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["api_ninjas"] 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 API Ninjas-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit api_ninjas |
| 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 |
API Ninjas Automation via Rube MCP
Automate API Ninjas operations through Composio's API Ninjas toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/api_ninjas