How do I ensure current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing; tool schemas change, so do not hardcode slugs or arguments.

What if the News API connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with the news_api toolkit to activate and complete any auth steps, then re-run with ACTIVE status.

Do I need to include memory in tool calls?

Yes. Include memory (even if empty {}) in every RUBE_MULTI_EXECUTE_TOOL call.

news-api-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/news-api-automation --openclaw

Files (1)

SKILL.md

2.9 KB

News API Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/news_api

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active News API connection via RUBE_MANAGE_CONNECTIONS with toolkit news_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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit news_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: "News 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 News API task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["news_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 News API-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `news_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/news-api-automation/SKILL.mdView on GitHub

Overview

This skill automates News API operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure up-to-date inputs and execution plans.

How This Skill Works

Technically, you start by verifying RUBE MCP connectivity with RUBE_SEARCH_TOOLS, then check or establish a News API connection via RUBE_MANAGE_CONNECTIONS with toolkit news_api, and finally execute discovered tools using RUBE_MULTI_EXECUTE_TOOL. Workflows should include a memory object and a session_id, and you should reuse session IDs where appropriate.

When to Use It

When you need to automate repetitive News API operations (fetch, filter, and summarize) across sources.
When tool schemas or slugs may change—always fetch current schemas before execution.
When setting up and validating News API connections, ensuring status is ACTIVE.
When building multi-step workflows that require session continuity.
When performing bulk or paginated fetches across many sources.

Quick Start

Step 1: Ensure Rube MCP is connected and that RUBE_SEARCH_TOOLS responds.
Step 2: Discover available tools for your News API task using RUBE_SEARCH_TOOLS.
Step 3: Check the connection, then execute tools with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify the connection status via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact input field names and types from search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens until complete.

Example Use Cases

Schedule a daily top-headlines fetch and store summaries in your CMS.
Retrieve articles from multiple sources with pagination and generate a consolidated report.
Validate and refresh the News API connection when credentials rotate.
Run a multi-tool workflow to fetch article metadata and short summaries for a topic.
Bulk fetch articles and export to an analytics pipeline for analysis.

Frequently Asked Questions

Add this skill to your agents