Skip to main content
Glama

search_prompts

Search booru image boards by tags and retrieve ready-to-use, cleaned AI-art prompts, each with category splits for appearance, clothing, pose, scenery, character, quality, and other.

Instructions

Search an image booru (Danbooru/AIBooru/e621/Gelbooru/Rule34) by TAG and return ready-to-use, cleaned AI-art prompts. Each result has the full prompt string plus its category split (appearance/clothing/pose/scenery/character/quality/other). This is the recommended tool for finding 'ready-to-use AI painting tags'.

== WHEN TO USE A DIFFERENT TOOL INSTEAD ==

  • 'What does character X look like?' / 'list costume variants of X' / 'what tags describe X' -> use danbooru_get_character_profile (one call: trait frequency table + wiki + bidirectional implications). It is built for describing a known character, while search_prompts returns sample images each turned into a prompt — different goals.

  • 'Find the canonical tag name for a Chinese/Japanese term or a misspelling' -> use autocomplete_tags (alias/fuzzy/other_names aware).

== SEARCH SEMANTICS — read this before calling ==

  • This is NOT a keyword-search engine like Google. You query with one or more booru TAGS, and results are images ALL of whose tags are present.

  • A booru tag is a single token, multi-word tags use UNDERSCORE: 'blue_hair', 'hatsune_miku', 'sitting_on_chair' — never 'blue hair'.

  • MULTI-TAG SEARCH IS SUPPORTED but each provider caps how many plain tags you may combine per query: danbooru/aibooru/e621 = 2, gelbooru/rule34 = 10 (metatags like order:rank or rating:safe do not count). Exceeding the limit returns an error telling you how to fix it; you can also raise a provider's cap with the BOORU_MAX_TAGS_ env var (e.g. BOORU_MAX_TAGS_DANBOORU=6 for a Gold account).

  • STRONGLY PREFER A SINGLE TAG to start. 'hatsune_miku' returns thousands of well-tagged images; 'hatsune_miku blue_hair school_uniform smile' is treated as AND → dramatically fewer results (often zero). The cleaned prompt already contains far more detail than your search tag, so adding search tags is at best redundant and at worst returns nothing.

  • When you need a pure-quality / generalized set (no specific character or franchise yet), search '1girl' or '1boy' alone, or use 'random' order.

  • Do not write natural-language queries ('a girl with blue hair sitting in a classroom') — that is not supported. Translate to booru tags first.

  • Use autocomplete_tags if you are not sure how a concept is spelled as a booru tag (e.g. user said '法国女仆' → try 'french', 'maid' and let autocomplete return 'french maid', 'maid_uniform', etc.).

  • Common useful single-tag starting points: a character tag ('hatsune_miku'), an artist tag, a copyright tag ('blue_archive'), a character + single qualifier ('2girls' for group shots), or 'order:rank' / 'random' for non-themed browsing via order param.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
tagsYes
limitNo
orderNopopular
ratingNoall
excludeNo
optimizeNo
providerNodanbooru
added_tagsNo
random_seedNo
min_tag_countNo
background_modeNokeep
include_previewNo
resolve_conflictsNo
include_charactersNo
include_copyrightsNo
simple_background_replacement_tagsNo
Behavior5/5

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

With no annotations, the description carries the full burden of disclosure. It explains non-obvious behavior: this is not keyword search, multi-tag queries are ANDed, providers cap plain tags, exceeding the limit returns an error, and the env var can raise the cap. It also discloses the return format with category splits. No contradiction with annotations exists.

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 long but tightly organized with clear headings ('WHEN TO USE A DIFFERENT TOOL INSTEAD', 'SEARCH SEMANTICS') and every sentence contributes actionable guidance. The purpose is front-loaded in the first sentence, and no filler or redundant phrases appear.

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

Completeness5/5

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

Given the tool's complexity (17 parameters, 5 providers, no output schema or annotations), the description covers all essential invocation aspects: tag syntax, query semantics, provider-specific limits, alternatives, and return value shape. It even provides common starting-point tags, making it fully usable for an agent to select and call correctly.

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?

The schema has 0% parameter descriptions, so the description must compensate. It thoroughly explains the critical `tags` parameter (underscore format, AND semantics, per-provider caps), `order` (order:rank, random), `provider` (the booru list), and rating metatags. However, several parameters (page, limit, exclude, optimize, background_mode, etc.) are left to their names alone, preventing a perfect score.

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 opens with a precise verb and resource: 'Search an image booru (Danbooru/AIBooru/e621/Gelbooru/Rule34) by TAG and return ready-to-use, cleaned AI-art prompts.' It also specifies the output shape (full prompt string plus category split), which clearly differentiates it from sibling tools like search_posts and build_prompt.

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?

An explicit 'WHEN TO USE A DIFFERENT TOOL INSTEAD' section names alternatives (danbooru_get_character_profile, autocomplete_tags) and explains exactly when they are preferable. The 'SEARCH SEMANTICS' section gives concrete usage rules: prefer a single tag, avoid natural-language queries, use underscores, and consult autocomplete_tags for uncertain spellings.

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/echo-xianyu/Booru-Pictag-Get-MCP'

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