Microsoft_clarity Automation
Automate Microsoft_Clarity operations using Rube MCP and Composio toolkit.
Install
npx promptshop add microsoft_clarity-automationDetails
What This Skill Does
This skill automates Microsoft Clarity operations using the Composio Microsoft Clarity toolkit via Rube MCP. It enables users to automate tasks related to session recordings, heatmaps, and user behavior analytics within Microsoft Clarity. The skill requires an active Microsoft Clarity connection and Rube MCP setup.
When to Use
- Discover available Microsoft Clarity tools.
- Execute specific Microsoft Clarity operations.
- Automate session recording analysis.
- Generate heatmaps for user behavior insights.
- Analyze user interaction patterns.
- Create multi-step workflows for Clarity tasks.
Key Features
- Discovers tools via RUBE_SEARCH_TOOLS.
- Executes tools with RUBE_MULTI_EXECUTE_TOOL.
- Supports multi-step workflows.
- Requires active Microsoft Clarity connection.
- Provides examples for tool discovery.
- Offers insights into user behavior analytics.
Manual Installation
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Microsoft Clarity connection via RUBE_MANAGE_CONNECTIONS with toolkit microsoft_clarity 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 microsoft_clarity 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": "session recordings, heatmaps, and user behavior analytics", "known_fields": ""}]
This returns: Available tool slugs for Microsoft Clarity Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool
Core Workflows
1. Discover Available Microsoft Clarity Tools
RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Microsoft Clarity tools and capabilities"
Review the returned tools, their descriptions, and input schemas before proceeding.
2. Execute Microsoft Clarity 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 Microsoft Clarity operations:
Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses 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 Thread PoolExecutor 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 Microsoft Clarity 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 schema Ref is returned instead of input_schema.
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Microsoft Clarity-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit microsoft_clarity |
| 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 schema Ref |
Toolkit docs: composio.dev/toolkits/microsoft_clarity Microsoft Clarity Automation via Rube MCP
Automate Microsoft Clarity operations through Composio's Microsoft Clarity toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/microsoft_clarity
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Microsoft Clarity connection via RUBE_MANAGE_CONNECTIONS with toolkit microsoft_clarity 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 microsoft_clarity 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": "session recordings, heatmaps, and user behavior analytics", "known_fields": ""}]
This returns: Available tool slugs for Microsoft Clarity Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool
Core Workflows
1. Discover Available Microsoft Clarity Tools
RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Microsoft Clarity tools and capabilities"
Review the returned tools, their descriptions, and input schemas before proceeding.
2. Execute Microsoft Clarity 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 Microsoft Clarity operations:
Search for all relevant tools: RUBE_SEARCH_TOOLS with specific use case Execute prerequisite steps first (e.g., fetch before update) Pass data between steps using tool responses 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 Thread PoolExecutor 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 Microsoft Clarity 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 s