JSONPlaceholder MCP Server
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_postsC | Retrieve all posts or a specific post by ID from JSONPlaceholder |
| get_usersC | Retrieve all users or a specific user by ID |
| get_commentsB | Retrieve comments, optionally filtered by post ID or get a specific comment |
| get_albumsB | Retrieve albums, optionally filtered by user ID or get a specific album |
| get_photosB | Retrieve photos, optionally filtered by album ID or get a specific photo |
| get_todosB | Retrieve todos, optionally filtered by user ID or get a specific todo |
| create_postB | Create a new post (simulated - JSONPlaceholder doesn't actually store data) |
| search_postsC | Search posts by title or body content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_post | Generate a prompt to analyze a specific post |
| user_profile_summary | Generate a prompt to create a comprehensive user profile summary |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_all_posts | Get all posts from JSONPlaceholder |
| get_all_users | Get all users from JSONPlaceholder |
TDQS
Scored across 8 tools
Most tools are clearly distinct by resource type (posts, albums, comments, photos, todos, users), but 'get_posts' and 'search_posts' have overlapping purposes since both retrieve posts with different filtering approaches. The descriptions help clarify the distinction, but an agent might occasionally misselect between them.
All tools follow a consistent verb_noun pattern with 'create_' or 'get_' or 'search_' prefixes, all in snake_case. This predictability makes it easy for agents to understand and use the tool set without confusion.
With 8 tools, this server is well-scoped for interacting with JSONPlaceholder's mock REST API resources. Each tool corresponds to a key resource (posts, albums, comments, photos, todos, users), and the count is neither too sparse nor bloated for the domain.
The server covers retrieval (get) operations for all major resources and creation for posts, but lacks update and delete operations, which are typical in CRUD workflows. This creates notable gaps that agents must work around, as they cannot modify or remove data beyond creating posts.