asin-data-api-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/asin-data-api-automation --openclawAsin Data API Automation via Rube MCP
Automate Asin Data API operations through Composio's Asin Data API toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/asin_data_api
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Asin Data API connection via
RUBE_MANAGE_CONNECTIONSwith toolkitasin_data_api - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitasin_data_api - 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: "Asin Data API 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 Asin Data API task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["asin_data_api"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Asin Data API-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit asin_data_api |
| 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/asin-data-api-automation/SKILL.mdView on GitHub Overview
Automate Asin Data API operations through Composio toolkit using Rube MCP. Always search for current schemas with RUBE_SEARCH_TOOLS before running workflows and manage your connection with RUBE_MANAGE_CONNECTIONS. This approach standardizes setup and execution for reliable, schema-aware automation.
How This Skill Works
The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and schemas. It then checks the connection status via RUBE_MANAGE_CONNECTIONS and, when ACTIVE, executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the discovered slug, schema-compliant arguments, memory, and a session_id. Always include memory in calls and reuse session IDs within a workflow for reliability.
When to Use It
- Automate repetitive Asin Data API operations across many ASINs in a single session
- After a tool schema change, use RUBE_SEARCH_TOOLS to locate updated slugs and fields
- Before batch runs, verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE
- Perform bulk operations using RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH for orchestration
- Reuse a session ID to maintain context across sequential Asin Data API tasks
Quick Start
- Step 1: Ensure Rube MCP is connected by running RUBE_SEARCH_TOOLS
- Step 2: Manage the asin_data_api connection with RUBE_MANAGE_CONNECTIONS
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool via RUBE_MULTI_EXECUTE_TOOL using a discovered slug, proper arguments, memory, and a session_id
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current schemas
- Verify ACTIVE status with RUBE_MANAGE_CONNECTIONS before executing tools
- Use exact field names and types from the search results and avoid hardcoding
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs within a workflow; generate new ones for separate runs
Example Use Cases
- Nightly ASIN metrics pull: discover tools, verify connection, and execute the appropriate tool to fetch data for top 100 ASINs
- Schema update adaptation: after RUBE_SEARCH_TOOLS reveals new input fields, adjust the workflow and re-run
- Batch price updates: process a batch of ASINs with RUBE_MULTI_EXECUTE_TOOL and store results
- Paginated results handling: continue fetching until the API returns no next page token
- Connection health check: routinely verify RUBE_MANAGE_CONNECTIONS ACTIVE before automation
