yominpost-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_postsA | Generate platform-specific social posts from brand material. Runs YominPost's 8-slot pipeline (brand DNA → trends → ideation → format router → copy → visual → short-video storyboard → QA self-critique). Works offline with no API key; uses a real model if the server was configured with one (YOMINPOST_PROVIDER / ANTHROPIC_API_KEY). Args: brand: brand or product name. material: what the brand does / the announcement / notes to write from. platforms: any of x, linkedin, instagram, tiktok, youtube, xiaohongshu, wechat. Default ["x"]. num_topics: number of post ideas (1-10). trends: optional trend signals to weave in. language: auto (follow the material), en or zh. |
| check_postA | Pre-publish risk check for one post: prompt leaks, engagement bait, hashtag stuffing, link stacking and platform length limits. ok=false means do not publish as-is. |
| list_platformsA | List generation targets and publishing channels (which ones publish for real and how they authenticate). |
| save_draftA | Save a post as a DRAFT in the local YominPost workspace, targeting the connected channels for the given platforms. It is not published; the user reviews and publishes it in the web UI. |
| list_postsB | List posts in the local workspace. status: draft | scheduled | posted | failed (empty = all). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly distinct action on the post lifecycle: generation, risk-checking, platform discovery, draft persistence, and listing. There is a slight question of whether generate_posts persists output, but save_draft explicitly owns persistence, so the boundary is legible.
All five names follow a consistent verb_noun snake_case pattern (generate_posts, check_post, list_platforms, save_draft, list_posts). The only trivial deviation is singular 'check_post' vs plural 'list_posts', which is still readable and predictable.
Five tools is well-scoped for a focused social-post generation and drafting server, with no redundant or filler tools. Each tool covers a distinct stage of the pipeline rather than duplicating capability.
Core lifecycle coverage is present: generate, validate, save draft, list posts, and discover platforms. Publishing is deliberately delegated to the web UI, but there is no get-single-post, update/edit, or delete tool, which leaves minor lifecycle gaps an agent must work around.