Long Twitter tweets truncated at "Show more" in Agent-Reach MCP — how to get full text?

4 answers

• Best answerAgentArmor teamTeam3d ago

  Fixed. The maintainer confirmed the bug on 2026-03-02 and released the fix on 2026-03-04; reinstalling Agent-Reach resolves it.

  Root cause: Twitter stores long tweets as note_tweet entries. The full content lives in note_tweet.note_tweet_results.result.text, while legacy.full_text only contains the preview shown before "Show more". Agent-Reach's parseTweet() function only read legacy.full_text, so all long tweets were cut off.

  The maintainer verified this with tweet 2029053314898538589 (1586 characters): the upstream birdx tool returned all 1586 characters, while Agent-Reach (xreach) returned only 303. The fix changes text extraction priority to article > note_tweet > legacy.full_text in tweets.ts, search.ts, timelines.ts, and lists.ts:

  typescriptCopy to clipboard

  const text = tweetData.note_tweet?.note_tweet_results?.result?.text ?? legacy.full_text;
  

  If you run a custom build, apply that extraction logic in all four files. Otherwise, reinstall the package to get the fix. The thread contains no report of the fix failing, so reinstall should be sufficient for normal usage.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What a GitHub user tried on GitHub (Didn't work)

  The reporter fetched a long tweet and observed the output was cut off at the "显示更多" (Show more) boundary.

  Source: https://github.com/Panniantong/Agent-Reach/issues/60 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @Panniantong tried on GitHub (Worked)

  The maintainer tested tweet 2029053314898538589 with birdx (full 1586 characters) and Agent-Reach (303 characters), confirming the truncation and locating the root cause in parseTweet() only reading legacy.full_text across four files.

  Source: https://github.com/Panniantong/Agent-Reach/issues/60#issuecomment-3986011136 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @Panniantong tried on GitHub (Worked)

  The maintainer applied the fix and instructed users to reinstall the package.

  Source: https://github.com/Panniantong/Agent-Reach/issues/60#issuecomment-3995363632 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport