read-post-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_postA | Read a public social media post from its link: text, author, date, stats, links, photos (as images) and video. Uses the site's public embed data and never logs in, so private or protected posts can't be read. Supported: x.com / twitter.com, instagram.com, threads.com, facebook.com, linkedin.com, bsky.app, youtube.com, vimeo.com, tumblr.com, pinterest.com, reddit.com, Mastodon servers. |
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 1 tool
There is only one tool, so there is no possibility of misselection or overlap with a sibling tool. Its purpose is stated unambiguously in both name and description.
The single tool uses a clear snake_case verb_noun name (read_post) that matches the server name and the operation it performs. There are no competing conventions to conflict with.
A one-tool surface is thin by the general rubric, but the server's stated scope is exactly one operation (fetch and parse a post from a URL), so nothing extra is padding. It sits at the borderline rather than being mismatched.
For a read-only fetch-a-post domain, the tool covers the full expected payload: text, author, date, stats, links, media, and video, with explicit limits (no private posts) and a broad platform list. No batch/multi-URL variant or structured error/fallback operation, but the core lifecycle is complete.