justserpapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUSTSERPAPI_API_KEY | Yes | Your JustSerpAPI API key. |
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 |
|---|---|
| search_endpointsA | Find JustSerpAPI endpoint candidates from natural language. Returns endpoint_id candidates; call get_endpoint_schema next. |
| get_endpoint_schemaA | Get the full schema and parameter contract for an endpoint_id returned by search_endpoints. |
| call_endpointB | Validate params and call a JustSerpAPI endpoint by endpoint_id. Params should use snake_case names from get_endpoint_schema. |
| list_servicesA | List supported JustSerpAPI services and endpoint counts. |
| refresh_catalogB | Admin-only. Refresh the endpoint catalog from JustSerpAPI OpenAPI documents. |
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 5 tools
Each tool has a clearly distinct purpose: list_services lists available services, search_endpoints finds endpoint candidates, get_endpoint_schema retrieves parameter details for a specific endpoint, call_endpoint executes the API call, and refresh_catalog updates the endpoint catalog. There is no ambiguity or overlap between tools.
All tool names follow a consistent verb_noun pattern using snake_case: list_services, search_endpoints, get_endpoint_schema, call_endpoint, refresh_catalog. The naming style is uniform and predictable.
With 5 tools, the server is lightweight but well-scoped for its purpose of interacting with JustSerpAPI endpoints. It covers the essential workflow of discovering services, searching for endpoints, getting schemas, making calls, and refreshing data. The count feels appropriate, though slightly on the smaller side.
The tool set covers the core lifecycle: discovery (list_services, search_endpoints), parameter retrieval (get_endpoint_schema), execution (call_endpoint), and maintenance (refresh_catalog). There are minor gaps such as missing error handling or status checking tools, but the surface is complete enough for typical usage.