home / skills / composiohq / awesome-claude-skills / asin-data-api-automation

asin-data-api-automation skill

/asin-data-api-automation

This skill automates Asin Data API tasks through Rube MCP, ensuring tool schemas are discovered first and connections are active.

npx playbooks add skill composiohq/awesome-claude-skills --skill asin-data-api-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: asin-data-api-automation
description: "Automate Asin Data API tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Asin 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](https://composio.dev/toolkits/asin_data_api)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Asin Data API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `asin_data_api`
- 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 `asin_data_api`
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: "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_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 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](https://composio.dev)*

Overview

This skill automates Asin Data API operations using Composio’s toolkit via Rube MCP. It guides tool discovery, connection management, and safe execution patterns to run API tasks reliably. The workflow enforces live schema discovery and session-aware execution to avoid hardcoded calls and mismatches.

How this skill works

First, the skill queries RUBE_SEARCH_TOOLS to fetch the current tool slugs and input schemas for the Asin Data API toolkit. It then verifies or establishes an active connection with RUBE_MANAGE_CONNECTIONS and runs actions through RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH using the discovered schema-compliant arguments. Every execution includes session tracking and an explicit memory parameter.

When to use it

  • Running Asin Data API queries or updates programmatically via Rube MCP.
  • Automating bulk or paginated ASIN data retrieval and processing.
  • Integrating Asin Data API calls into larger composio workflows.
  • When tool schemas may have changed and live discovery is required.
  • Orchestrating multi-step flows that require session reuse and memory.

Best practices

  • Always call RUBE_SEARCH_TOOLS first to get current tool slugs and exact input schemas.
  • Verify connection status with RUBE_MANAGE_CONNECTIONS and complete any auth flows until ACTIVE.
  • Include a memory object (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
  • Reuse session IDs across a workflow; create new sessions for independent runs.
  • Handle pagination tokens from responses and iterate until all pages are fetched.

Example use cases

  • Discovering available Asin Data API endpoints and constructing schema-compliant requests.
  • Fetching product details for a list of ASINs with automated pagination handling.
  • Running bulk enrichment using RUBE_REMOTE_WORKBENCH and run_composio_tool() for large datasets.
  • Embedding Asin Data API calls inside a multi-tool composio automation with consistent session context.
  • Performing periodic syncs where tool schemas might evolve between runs.

FAQ

What is the first call I should make when running a workflow?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and their exact input schemas before any execution.

Do I need API keys to use Rube MCP?

No API keys are required for the Rube MCP endpoint; add https://rube.app/mcp as an MCP server in your client configuration.

What if my connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then confirm the connection shows ACTIVE before running tools.