Gemini Automation

What This Skill Does

This skill automates Gemini operations using the Composio Gemini toolkit through Rube MCP. It is designed for users who need to streamline and automate tasks within the Gemini platform. The skill simplifies interaction with Gemini by providing tools for connection management, tool discovery, and execution.

When to Use

Automate Gemini workflows. Discover available Gemini tools. Check Gemini connection status. Execute Gemini tools with schema-compliant arguments. Integrate Gemini operations into existing workflows. Dynamically adapt to Gemini tool schema changes.

Key Features

Connects to Gemini via Rube MCP.Discovers available Gemini tools and their schemas. Manages Gemini connection status. Executes Gemini tools with provided arguments. Provides a structured workflow pattern for Gemini automation. Offers guidance on avoiding common pitfalls.

Gemini Automation via Rube MCP

Automate Gemini operations through Composio's Gemini toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/gemini

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Gemini connection via RUBE_MANAGE_CONNECTIONS with toolkit gemini 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 gemini 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: "Gemini 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 Gemini task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["gemini"] 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