joj-image-search
Server Details
Image Search: Fast and Simple Image Search API. You can get 100+ search results in one query!.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.2/5 across 1 of 1 tools scored.
With only a single tool, there is no possibility of confusion or overlap, so the tool is trivially distinguishable.
The tool name 'get_v2' uses a consistent lowercase with underscore style, but it lacks a descriptive term like 'search_images' and the 'v2' suffix is unclear. However, since it's the only tool, there's no inconsistency to penalize heavily.
A single tool for an image search service is minimal and feels thin. While it may be appropriate for a narrow API, it falls below the typical 3-15 range for a well-scoped server.
The tool only provides search functionality. A complete image search API would likely include operations like retrieving image details, uploading, or managing collections, so significant gaps exist in the surface.
Available Tools
1 toolget_v2Search V2CInspect
Search V2 Group: Image Search. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search query. You can use search parameters. e.g. `adele site:youtube.com` e.g. `query -exclude` | |
| hl | No | Language code for search. Default: en | |
| tbs | No | Search filters. | |
| nfpr | No | ||
| safe | No | If you want safe search, set it to `active` | |
| cursor | No | Cursor for next results. | |
| filter | No | ||
| suggestion_query | No | Suggestion query (must be taken from response suggestions). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for disclosing behavior. It only mentions search and billing, but does not describe return formats, pagination, authentication, side effects, or any operational constraints. This is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence that efficiently conveys the primary function and a cost detail. It is not overly verbose, though it sacrifices substance for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 8 parameters, no output schema, and no sibling context, yet the description provides no information about return values, pagination, error handling, or how results are presented. It is far from sufficient for an agent to use without external knowledge.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds zero information about parameters. Although the input schema has descriptions for 6 of 8 parameters (75% coverage), this is not high enough to fully rely on schema alone. The description does not compensate for the two undocumented parameters (nfpr, filter) or clarify usage intent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Image Search', providing a clear verb and resource. It indicates it is a search tool for images, which is distinct from generic web search, even though no sibling tools are listed for comparison. However, it does not elaborate beyond that.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description only includes a billing note, which does not help an agent decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityCmaintenanceEnables users to compare images for visual similarity, detect exact and near-duplicates, and obtain similarity scores and perceptual hash distances via a plain HTTP API.

OpenSERP Cloudofficial
AlicenseBqualityCmaintenanceSearch API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia results with URL extraction (+image search and engine metadata tools)9872MIT- Alicense-qualityDmaintenanceA search service based on multiple image APIs and icon generation capabilities, specifically designed for integration with Cursor MCP service. Supports image search, download, and AI-generated icons.16MIT
- AlicenseAqualityCmaintenanceEnables AI agents to perform Google searches and retrieve structured JSON results for 10 types including web, images, news, and shopping with live prices. Offers 1,000 free searches per month with no credit card required.129MIT