Social PostLint-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 |
|---|---|
| check_postA | Check a social post against one platform's real character limit and report whether it fits. Returns the counted length, the limit, and what drove the count (URLs billed at a fixed width, non-Latin characters billed double, emoji sequences collapsed to one grapheme). Use this before publishing anything with a hard limit — the counting rules are per-platform and are not text.length. |
| check_post_allA | Check one post against every platform at once and get a row per platform: counted length, limit, and whether it fits. Use this when deciding where a draft can go as-is. The per-platform arithmetic is included only for the platforms it fails, to keep the response small — call check_post for a single platform's full breakdown. |
| platform_limitsA | List the platforms this server knows, with each one's limit, the unit it is measured in, why that unit is not a plain character count, and the source the number came from. Use it to explain a result or to see what is covered. |
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 3 tools
Each tool has a distinct purpose: check_post for a single platform's detailed breakdown, check_post_all for a summary across platforms, and platform_limits for reference data. There is no ambiguity between them, as the scope and output format are clearly differentiated.
The main actions follow a verb_noun pattern: check_post and check_post_all. The third tool, platform_limits, is a noun phrase rather than an action, but it fits the resource-based naming convention and is still intuitive. Minor deviation, but overall the naming is predictable and readable.
Three tools perfectly cover the server's narrow scope of checking social post limits. Each tool is essential and non-redundant, and the count feels neither too thin nor excessive for a linting utility.
The set covers the full workflow: check one platform, check all platforms, and query platform metadata. The only minor gap is the lack of a tool to add or modify platform definitions, but for a linting server this is a reasonable boundary and not a practical dead end.