Skip to content

ComposioHQ/awesome-claude-skills / composio-skills/google_maps-automation

google_maps-automation

Verified

Automate Google Maps tasks via Rube MCP (Composio): geocoding, directions, place search, and distance calculations. Always search tools first for current schemas.

Google Maps Automation via Rube MCP

Automate Google Maps operations through Composio's Google Maps toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/google_maps

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Google Maps connection via RUBE_MANAGE_CONNECTIONS with toolkit google_maps
  • 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 google_maps
  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": "geocoding, directions, place search, and distance calculations", "known_fields": ""}]

This returns:

  • Available tool slugs for Google Maps
  • Recommended execution plan steps
  • Known pitfalls and edge cases
  • Input schemas for each tool

Core Workflows

1. Discover Available Google Maps Tools

RUBE_SEARCH_TOOLS:
  queries:
    - use_case: "list all available Google Maps tools and capabilities"

Review the returned tools, their descriptions, and input schemas before proceeding.

2. Execute Google Maps Operations

After discovering tools, execute them via:

RUBE_MULTI_EXECUTE_TOOL:
  tools:
    - tool_slug: "<discovered_tool_slug>"
      arguments: {<schema-compliant arguments>}
  memory: {}
  sync_response_to_workbench: false

3. Multi-Step Workflows

For complex workflows involving multiple Google Maps operations:

  1. Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case
  2. Execute prerequisite steps first (e.g., fetch before update)
  3. Pass data between steps using tool responses
  4. Use RUBE_REMOTE_WORKBENCH for bulk operations or data processing

Common Patterns

Search Before Action

Always search for existing resources before creating new ones to avoid duplicates.

Pagination

Many list operations support pagination. Check responses for next_cursor or page_token and continue fetching until exhausted.

Error Handling

  • Check tool responses for errors before proceeding
  • If a tool fails, verify the connection is still ACTIVE
  • Re-authenticate via RUBE_MANAGE_CONNECTIONS if connection expired

Batch Operations

For bulk operations, use RUBE_REMOTE_WORKBENCH with run_composio_tool() in a loop with ThreadPoolExecutor for parallel execution.

Known Pitfalls

  • Always search tools first: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via RUBE_SEARCH_TOOLS.
  • Check connection status: Ensure the Google Maps connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication.
  • Respect rate limits: If you receive rate limit errors, reduce request frequency and implement backoff.
  • Validate schemas: Always pass strictly schema-compliant arguments. Use RUBE_GET_TOOL_SCHEMAS to load full input schemas when schemaRef is returned instead of input_schema.

Quick Reference

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Google Maps-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit google_maps
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Toolkit docs: composio.dev/toolkits/google_maps

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall