Nodes/ComfyUI_e621_booru_toolkit/[OLD] Tag Wiki Lookup
ComfyUI Node

[OLD] Tag Wiki Lookup

Answer 'what does this tag even mean' without leaving ComfyUI

By DraconicDragon·Created 2 years ago·Updated 3 months ago· 7
[OLD] Tag Wiki Lookup
    • STRING
    tags
    boorudanbooru
    extended_infono

    Somewhere in every tag-prompting workflow there's a moment where a post makes no sense and you need to know what the tag actually means. Tag Wiki Lookup is the pack's answer: paste a tag, get the wiki description from Danbooru or e621, read it, move on. It's marked [OLD], it's barebones, and the author himself says the output is "probably enough for most people" - which is a fair summary. This is a utility node, not a showpiece.

    It's an output node with a small party trick: a Fetch Wiki button on the node itself that runs without queuing, showing the text in a read-only textbox. So you don't have to push your whole workflow through the sampler just to check a tag - a genuinely nice touch for a node this simple.

    How it works

    The node normalizes whatever you type - spaces to underscores, backslashes stripped, extra underscores collapsed - then asks the selected board's wiki API. Danbooru and e621/e6ai/e926 are the two options in the booru dropdown, each using its own endpoint and parameter shape. One honest limitation to know before you rely on it: it only handles the first tag. Feed it a comma-separated list and everything after the first comma is ignored. The tooltip says so, and it's worth taking seriously.

    The extended_info dropdown (yes / no / only_extended) controls trimming. Wiki pages are long and full of formatting, so with no (the default) it cuts the description at the first subheading - that's the practical "what is this tag" answer. yes returns the whole body, and only_extended gives you just the cut-off tail. It's crude, but it works.

    Inputs and output

    • tags - the tag to look up (first tag wins).
    • booru - danbooru or e621, e6ai, e926.
    • extended_info - how much of the wiki body to return.

    The single output is a STRING with the wiki text. Since it's an output node you can also wire it anywhere a string is expected - into a text display, a file writer, whatever - but the in-node textbox is the intended use.

    Install

    Same pack, same routine:

    cd ComfyUI/custom_nodes
    git clone https://github.com/DraconicDragon/ComfyUI_e621_booru_toolkit
    

    restart ComfyUI (or search the pack in ComfyUI Manager). Dependencies are the light set - requests, pillow, curl_cffi - and the wiki fetch itself rides on a small server endpoint the pack registers.

    Gotchas

    The output is raw wiki body text, so expect markdown and booru formatting noise rather than clean prose - the trimming is the only cleanup it does. The [OLD] tag means the author treats it as legacy, so don't lean on it inside an automation loop that queues hundreds of lookups; the boards rate-limit. For a one-off "what does this tag mean," it does the job without a browser tab, and that's about all it promises.

    CategoryE621 Booru Toolkit/Tags

    Inputs (3)

    NameTypeDefaultDescription
    tagsSTRINGEnter the tags to search for, separated by commas.Input tags are normalized meaning you don't need to pay attention to using underscores or backslashes or having to worry about too many spaces.(Important: currently only supports a single tag. If multiple are supplied then one before first comma is chosen.)
    booruCOMBOdanbooruSelect the booru to search for the tag wiki page.
    extended_infoCOMBOnoInclude extended info of the wiki page response, mostly useless for now.

    Outputs (1)

    NameTypeDescription
    STRINGSTRING