Skip to main content
Glama
acchuang

Jina AI Remote MCP Server

by acchuang

search_images

Find web images for concepts, illustrations, or specific pictures using search terms. Returns images as base64-encoded JPEGs by default or provides URLs and metadata when specified.

Instructions

Search for images across the web, similar to Google Images. Use this when you need to find photos, illustrations, diagrams, charts, logos, or any visual content. Perfect for finding images to illustrate concepts, locating specific pictures, or discovering visual resources. Images are returned by default as small base64-encoded JPEG images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesImage search terms describing what you want to find (e.g., 'sunset over mountains', 'vintage car illustration', 'data visualization chart')
return_urlNoSet to true to return image URLs, title, shapes, and other metadata. By default, images are downloaded as base64 and returned as rendered images.
tbsNoTime-based search parameter, e.g., 'qdr:h' for past hour, can be qdr:h, qdr:d, qdr:w, qdr:m, qdr:y
locationNoLocation for search results, e.g., 'London', 'New York', 'Tokyo'
glNoCountry code, e.g., 'dz' for Algeria
hlNoLanguage code, e.g., 'zh-cn' for Simplified Chinese

Implementation Reference

  • Handler for the 'search_image' tool (note: queried tool is 'search_images' but implementation is 'search_image'). Performs API call to Jina image search endpoint with query, handles authentication and errors, returns YAML serialized results.
    		try {
    			const props = getProps();
    
    			const tokenError = checkBearerToken(props.bearerToken);
    			if (tokenError) {
    				return tokenError;
    			}
    
    			const response = await fetch('https://svip.jina.ai/', {
    				method: 'POST',
    				headers: {
    					'Accept': 'application/json',
    					'Content-Type': 'application/json',
    					'Authorization': `Bearer ${props.bearerToken}`,
    				},
    				body: JSON.stringify({
    					q: query,
    					type: 'images',
    				}),
    			});
    
    			if (!response.ok) {
    				return handleApiError(response, "Image search");
    			}
    
    			const data = await response.json() as any;
    
    			return {
    				content: [
    					{
    						type: "text" as const,
    						text: yamlStringify(data.results),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text" as const,
    						text: `Error: ${error instanceof Error ? error.message : String(error)}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	},
    );
  • Input schema for search_image tool using Zod: requires a 'query' string parameter.
    	query: z.string().describe("Image search terms describing what you want to find (e.g., 'sunset over mountains', 'vintage car illustration', 'data visualization chart')")
    },
    async ({ query }: { query: string }) => {
  • Registration of the search_image tool within registerJinaTools function.
    	"search_image",
    	"Search for images across the web, similar to Google Images. Use this when you need to find photos, illustrations, diagrams, charts, logos, or any visual content. Perfect for finding images to illustrate concepts, locating specific pictures, or discovering visual resources. Returns image search results with URLs, titles, descriptions, and image metadata.",
    	{
    		query: z.string().describe("Image search terms describing what you want to find (e.g., 'sunset over mountains', 'vintage car illustration', 'data visualization chart')")
    	},
    	async ({ query }: { query: string }) => {
    		try {
    			const props = getProps();
    
    			const tokenError = checkBearerToken(props.bearerToken);
    			if (tokenError) {
    				return tokenError;
    			}
    
    			const response = await fetch('https://svip.jina.ai/', {
    				method: 'POST',
    				headers: {
    					'Accept': 'application/json',
    					'Content-Type': 'application/json',
    					'Authorization': `Bearer ${props.bearerToken}`,
    				},
    				body: JSON.stringify({
    					q: query,
    					type: 'images',
    				}),
    			});
    
    			if (!response.ok) {
    				return handleApiError(response, "Image search");
    			}
    
    			const data = await response.json() as any;
    
    			return {
    				content: [
    					{
    						type: "text" as const,
    						text: yamlStringify(data.results),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text" as const,
    						text: `Error: ${error instanceof Error ? error.message : String(error)}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	},
    );
  • src/index.ts:21-22 (registration)
    Top-level registration call in MyMCP.init() that registers all Jina tools including search_image.
    	registerJinaTools(this.server, () => this.props);
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the tool searches across the web, returns images by default as small base64-encoded JPEGs, and offers an option to return URLs and metadata. However, it lacks details on rate limits, authentication needs, or potential costs, which are important for an agent to use the tool responsibly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose and usage guidelines. All sentences earn their place by adding value, such as clarifying the return format and use cases. However, it could be slightly more concise by combining some of the use-case examples into a single phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a 6-parameter tool with no annotations and no output schema, the description is somewhat complete but has gaps. It covers the purpose, usage, and return format well, but lacks details on error handling, pagination, or response structure, which would help an agent invoke the tool more effectively. The absence of an output schema increases the need for more descriptive context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning the default base64 encoding and URL/metadata option, but it does not provide additional context or examples for parameters like 'tbs' or 'location' that aren't already in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Search for images across the web') and resources ('images'), distinguishing it from siblings like search_web or search_arxiv by focusing exclusively on visual content. It explicitly mentions the similarity to Google Images, which provides immediate context about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use this tool ('when you need to find photos, illustrations, diagrams, charts, logos, or any visual content') and gives examples of use cases ('illustrate concepts, locating specific pictures, or discovering visual resources'). However, it does not explicitly state when NOT to use it or mention alternatives among the sibling tools, such as search_web for general web searches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/acchuang/jina-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server