Bug Description

The Twitter DM functionality in RUBE MCP is completely broken due to incorrect API parameter formatting. All attempts to fetch DM events fail with a parameter formatting error.

Error Message

{
  "errors": [{
    "parameters": {
      "event_types": ["ParticipantsJoin", "MessageCreate", "ParticipantsLeave"]
    },
    "message": "Repeating the `event_types` query parameter is not allowed. Pass multiple values as a single comma-separated string."
  }],
  "title": "Invalid Request",
  "detail": "One or more parameters to your request was invalid.",
  "type": "https://api.twitter.com/2/problems/invalid-request"
}

Root Cause

The RUBE tool wrapper for TWITTER_GET_RECENT_DM_EVENTS is sending array parameters to Twitter's API, but Twitter expects comma-separated strings.

Current behavior (broken):

"event_types": ["ParticipantsJoin", "MessageCreate", "ParticipantsLeave"]

Expected behavior (working):

"event_types": "ParticipantsJoin,MessageCreate,ParticipantsLeave"

Impact

• Complete feature failure: Cannot read any Twitter DM conversations
• Core functionality broken: DM features are unusable
• User experience: Twitter integration appears completely broken

Affected Tools

• TWITTER_GET_RECENT_DM_EVENTS - Primary tool affected
• Potentially other tools that use similar array-to-comma-separated-string parameters

Steps to Reproduce

1. Connect Twitter account to RUBE
2. Call TWITTER_GET_RECENT_DM_EVENTS with any parameters (or no parameters)
3. Observe API parameter formatting error
4. All calls fail regardless of parameter values

Expected Fix

The tool wrapper should convert array parameters to comma-separated strings before sending to Twitter's API:

// Convert arrays to comma-separated strings for Twitter API
if (Array.isArray(params.event_types)) {
  params.event_types = params.event_types.join(',');
}

Environment

• Client: Claude Code
• RUBE Version: Latest (via MCP)
• Twitter API: v2
• Date: September 20, 2025
• User: @danialhasan

Priority

HIGH - This breaks core Twitter DM functionality completely. Users cannot access any DM features through RUBE.

Additional Context

This affects all Twitter DM operations and makes the Twitter integration essentially useless for DM-related tasks. The error occurs even with minimal parameters or no parameters specified.

The issue appears to be in the parameter formatting layer between RUBE and Twitter's API, where arrays are not being converted to the expected comma-separated string format.

Thanks for looking into this!