No user-submitted related servers found.
Scored across 14 tools
Most tools map to a distinct resource+action (list connections, upload media, publish, schedule, update, delete, status, pipeline ops). The only real overlap is between generate_and_publish_post and the pair generate_social_content + publish_social_post, which do the same work in one call versus two; descriptions make the distinction clear but an agent could still hesitate. update_social_post vs update_content_progress target different objects (posts vs pipeline items) and are adequately separated by wording.
Every tool follows a consistent snake_case verb_noun pattern: list_*, get_*, generate_*, upload_*, publish_*, schedule_*, update_*, delete_*, add_*. The compound generate_and_publish_post is a slight deviation but still readable and follows the same convention.
14 tools sit comfortably in the well-scoped range and each covers a distinct stage of the workflow (connections, generation, media, publishing, scheduling, post CRUD, pipeline). Nothing appears redundant or padded beyond the single convenience wrapper.
Post lifecycle is fully covered (publish, schedule, list, status, update, delete) and the AI pipeline has ideas, listing, progress, and next-item retrieval. Gaps remain: connections are read-only (no connect/disconnect/refresh), media has upload but no list/delete, and there is no analytics/engagement retrieval for published posts, so agents cannot close the measurement loop.
