MCP TabNews Integration
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get statusC | get status from tabnews api |
| get contentsC | get contents from tabnews api |
| get contents by userC | get contents by user from tabnews api |
| get contentC | get content from tabnews api |
| get commentsC | get comments from a content on tabnews api |
| get analytics user createdB | To get how many users were created (per day) in tabnews |
| get analytics root content publishedB | To get how many posts were made (per day) in tabnews |
| get analytics child content publishedB | To get how many comments were made (per day) in tabnews |
| get rss feedB | To get the rss feed from tabnews |
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 9 tools
The tools have some overlap that could cause confusion, particularly between 'get content', 'get contents', and 'get contents by user', as their purposes are similar but not clearly distinct. However, the analytics tools and others like 'get rss feed' and 'get status' are well-separated, reducing overall ambiguity.
The naming is inconsistent, mixing descriptive phrases like 'get analytics child content published' with simpler forms like 'get content' and 'get status'. There is no uniform pattern, with variations in verb usage and structure, making it harder to predict tool names.
With 9 tools, the count is well-scoped for a TabNews integration, covering analytics, content retrieval, and system status without being overwhelming. Each tool appears to serve a specific purpose, making the set manageable and appropriate.
The toolset focuses heavily on read operations (get analytics, get content, get status) but lacks obvious write or update capabilities like creating or modifying content or comments. This creates notable gaps for a full integration, though core retrieval functions are covered.