jsonplaceholder-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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_postsA | Get posts from JSONPlaceholder. Can retrieve all posts, a specific post by ID, or filter by user ID. |
| get_usersA | Get users from JSONPlaceholder. Can retrieve all users or a specific user by ID. |
| get_commentsA | Get comments from JSONPlaceholder. Can retrieve all comments, a specific comment by ID, or comments for a specific post. |
| get_todosA | Get todos from JSONPlaceholder. Can retrieve all todos, a specific todo by ID, or filter by user ID. |
| create_postA | Create a new post on JSONPlaceholder. Note: This won't actually be saved to the server, but will simulate the creation. |
| update_postA | Update an existing post on JSONPlaceholder. Note: This won't actually update the server, but will simulate the update. |
| delete_postA | Delete a post on JSONPlaceholder. Note: This won't actually delete from the server, but will simulate the deletion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| JSONPlaceholder API Information | Information about the JSONPlaceholder API |
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: get_posts, get_users, get_comments, get_todos, create_post, update_post, delete_post. There is no overlap in purpose or behavior, and the descriptions make the boundaries clear.
All tool names follow a consistent verb_noun pattern: get_ for reads and create_/update_/delete_ for mutations. The pattern is uniform and predictable across the entire set.
With 7 tools, the server is well-scoped for a JSONPlaceholder demo. Each tool covers a core operation without unnecessary bloat, fitting comfortably in the ideal 3-15 tool range.
Posts have full CRUD coverage (get, create, update, delete), but users, comments, and todos are read-only. This leaves obvious gaps for mutating those resources, though the core post workflow is complete.