fix(social): correct search_social_posts response parsing - #21
fix(social): correct search_social_posts response parsing#21appressman wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The /posts/list API returns results nested under a `results` key
({ results: { posts, total } }) but the tool was reading response.data.posts
directly, always resolving to undefined and returning an empty list.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthrough
ChangesSocial Search Response Normalization
MCP Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Problem
search_social_postsalways returns an empty list (count: 0, posts: []) regardless of what's in the Social Planner.Root Cause
The
POST /social-media-posting/{locationId}/posts/listendpoint wraps its response under aresultskey:{ "results": { "posts": [...], "total": 99 } }The tool was reading
response.data?.postsdirectly, which is alwaysundefined— so every search silently returns nothing.Fix
src/tools/social-media-tools.ts— readsresponse.data?.results?.postswith fallback toresponse.data?.postsfor backwards compatibilitysrc/types/ghl-types.ts— addedresults?: { posts, total }toGHLSearchPostsResponseto match the actual API shapeTested against a live GHL location — confirmed 99 published posts returned correctly after the fix.
🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes