Skip to main content
Glama
limithacker

百度图片搜索 MCP Server

by limithacker

search_images

Search Baidu images, download selected results, and convert formats as needed.

Instructions

搜索百度图片,支持搜索、下载和格式转换一体化。

功能说明:

  1. 仅搜索模式:不指定 downloadPath,只返回图片信息(URL、尺寸、标题等)

  2. 搜索+下载模式:指定 downloadPath,自动下载图片到本地目录

  3. 格式转换:指定 format 参数,自动将图片转换为目标格式(仅下载模式有效)

使用示例:

  • 搜索图片:{ "keyword": "维多利亚港" }

  • 搜索第2页:{ "keyword": "长城", "page": 2 }

  • 下载缩略图:{ "keyword": "故宫", "downloadPath": "./downloads" }

  • 下载原图并转JPEG:{ "keyword": "黄山", "downloadPath": "./downloads", "format": "jpeg", "urlType": "original" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo页码,从 1 开始,默认 1
formatNo可选,指定输出图片格式。当下载的图片格式与指定格式不一致时自动转换。仅在设置 downloadPath 时有效
keywordYes搜索关键字(必填)
perPageNo每页数量,默认 30,最大 60
urlTypeNo选择下载使用的图片源。thumb=缩略图(默认,百度 CDN,稳定快速),original=原图(来源站点,可能有防盗链)。默认 thumbthumb
downloadPathNo可选,指定下载目录。设置后会将图片下载到该目录,否则只返回图片 URL 列表。例如:./downloads 或 /absolute/path
downloadFilenameNo可选,自定义下载文件名(不含扩展名,扩展名由 format 或图片原始格式决定)。多张图时自动追加索引后缀,例如指定 mypic 则保存为 mypic_1.jpg、mypic_2.jpg。仅在设置 downloadPath 时有效
Behavior4/5

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

Without annotations, the description discloses important behaviors: search-only returns metadata (URLs, sizes, titles), download mode saves files, format conversion applies only to downloads, and urlType notes anti-leech risks on original images. It could add error handling or return format details, but core behavioral traits are well covered.

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

Conciseness5/5

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

The description is concise yet structured with numbered modes and short examples. It front-loads the summary and avoids redundancy with the schema, making every sentence functional.

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

Completeness4/5

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

The tool has no output schema, but the description indicates what search-only mode returns. It doesn't specify download mode's return value or error cases, but overall it is quite complete for the tool's complexity, especially given the detailed input schema.

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

Parameters4/5

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

With 100% schema coverage, the schema already explains parameters, but the description enriches understanding by showing mode-dependent parameter interactions (e.g., format and downloadFilename only effective with downloadPath) and provides concrete examples that clarify parameter usage.

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 explicitly states the tool searches Baidu images and supports search, download, and format conversion. It clearly differentiates the three operational modes (search-only, download, format conversion) with specific verbs and resources.

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

Usage Guidelines5/5

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

The description provides explicit instructions for when to use each mode: omit downloadPath for search-only, specify it for download, and only use format with download. Concrete examples illustrate typical usage scenarios, making it easy to select the correct configuration.

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/limithacker/mcp_image_bd_tools'

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