content-distribution-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTENT_DIR | No | Path to content assets directory | ./content |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| draft_postA | Generate a post for a specific social platform (LinkedIn, Instagram, X/Twitter, TikTok). Uses StressZero brand rules: tutoiement, max 3 emojis, 3-5 hashtags, phrases courtes. Identity: Emmanuel Gomes Soares, Coach burnout entrepreneur. |
| repurpose_contentA | Take content from one platform and adapt it for another. Handles character limits (X: 280, LinkedIn: 3000, Instagram: 2200), hashtag styles, and format differences automatically. |
| generate_carouselA | Generate LinkedIn/Instagram carousel slides with title + body per slide. Supports educational, storytelling, and data-driven styles. |
| schedule_contentB | Save content to the publishing queue (content-queue.json). Stores the post with platform, scheduled date/time, and status. |
| get_content_calendarA | View the content calendar/queue. Shows all scheduled content for the next N days. |
| analyze_post_performanceA | Analyze a post's text for predicted engagement. Returns estimated engagement score (0-100), hook strength, CTA strength, readability, and actionable improvement suggestions. |
| generate_threadA | Generate a multi-post thread for X/Twitter or LinkedIn. Creates numbered posts with transitions, including hook, content posts, and CTA finale. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_content_sprint | Generate a week of content — 5 posts across platforms for StressZero Entrepreneur |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| content-queue | Current content publishing queue with scheduled posts across all platforms |
TDQS
Scored across 7 tools
The three content generation tools (draft_post, generate_carousel, generate_thread) serve distinct formats but could cause minor hesitation when choosing between single posts versus threads. However, platform-specific parameters and format descriptions provide adequate separation. Other tools have clearly distinct purposes (analysis, repurposing, calendar management).
All seven tools follow a consistent verb_noun snake_case convention (analyze_post_performance, draft_post, generate_carousel, etc.). The verb choices clearly indicate the action type (analyze, draft, generate, get, repurpose, schedule) without mixing styles or conventions.
Seven tools is an ideal count for a content distribution system, covering the full lifecycle from creation (3 tools), analysis, repurposing, and scheduling/retrieval. Each tool earns its place without redundancy or bloat.
While content creation and predictive analysis are well-covered, the scheduling system lacks update and delete operations for the content queue (only get_content_calendar and schedule_content exist). There's also no immediate publish or retrieve historical performance data, creating dead ends for calendar management workflows.