Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.
NewMaintained
Automatic
◆Data Engineer pack
Last verified 8/11/2026
What it changes
Passed 14 of 20 test cases with the skill, and 14 of 20 without it.
Without skill68%
With skill68%
Checks it passed that the model alone missed
Uses SEGMENT_ALIAS to link anon_9900 as previousId with usr_1100 as userId
Executes SEGMENT_ALIAS linking anon_4410 to usr_9011 before SEGMENT_IDENTIFY and SEGMENT_GROUP
2 fixed15 passed either way6 still failing2 broke
Pass-rate lift
0 pp
Tokens
+112%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/11/2026v117 of 25 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
An anonymous visitor 'anon_4410' browsed products, signed up as 'usr_9011', updated their profile, and then joined company 'grp_302'. What is the exact sequence of Segment API calls that represents this complete user lifecycle?
What was checked, without and with the skill
Checked
Without skill
With skill
Executes PAGE or TRACK calls with anonymousId prior to sign up
Passed
Passed
Executes SEGMENT_ALIAS linking anon_4410 to usr_9011 before SEGMENT_IDENTIFY and SEGMENT_GROUP
Missed
Passed
case-13 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md226 linessingle file
Segment Automation via Rube MCP
Automate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Segment connection via RUBE_MANAGE_CONNECTIONS with toolkit segment
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 segment
If connection is not ACTIVE, follow the returned auth link to complete Segment authentication
Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Track Events
When to use: User wants to send event data to Segment for downstream destinations
Tool sequence:
SEGMENT_TRACK - Send a single track event [Required]
Key parameters:
userId: User identifier (required if no anonymousId)
anonymousId: Anonymous identifier (required if no userId)
event: Event name (e.g., 'Order Completed', 'Button Clicked')
properties: Object with event-specific properties
timestamp: ISO 8601 timestamp (optional; defaults to server time)
context: Object with contextual metadata (IP, user agent, etc.)
Pitfalls:
At least one of userId or anonymousId is required
event name is required and should follow consistent naming conventions