Bing Search Tool

An LLM's knowledge stops at its training cutoff. Bing Search Tool is one of a few ways comfyui_LLM_party patches that gap - it wraps Microsoft's Bing Search API as a tool an agent node can call, so the model can go look something up instead of guessing. The pack's own README calls this out directly in its configuration section: if you want Google or Bing search tools working, you need to supply the relevant API key.

How it works

Same pattern as the pack's other search tools: this node doesn't run a search itself when the graph executes - it produces a tool definition that an LLM/agent node can invoke mid-conversation, deciding on its own when a search is actually needed rather than always running one.

The inputs and outputs that matter

• searchType - which Bing vertical to query: web, image, video, or news.
• bing_api_key (optional) - your Bing Search API key. Can be left off the node and set instead in the pack's config.ini, matching the README's documented setup for this exact key.
• custom_config_id / is_custom_api - support for pointing at a non-default or relay endpoint rather than Microsoft's standard API directly, following the same relay-friendly pattern the pack uses for its LLM API nodes (a custom base_url instead of the vendor default).
• is_enable - the standard bypass toggle.

Output: tool (STRING) - the tool descriptor. Wire it into the tool/tools input on the pack's LLM or agent node.

How to install it

Search comfyui_LLM_party in ComfyUI Manager and install, restart, then add your bing_api_key - either directly on the node or in the pack's config.ini file alongside your other provider keys (the README documents this exact setting there). Manual install:

cd ComfyUI/custom_nodes
git clone https://github.com/heshengtao/comfyui_LLM_party.git

Run pip install -r requirements.txt from the pack's own folder with ComfyUI's Python, then restart. This node needs no local model or heavy dependency of its own - the requirement is entirely the API key, not the install.

Common issues & troubleshooting

The agent never seems to search anything. Remember this node only builds a tool definition - it does nothing by itself. Confirm it's actually wired into your agent's tool input, and that the agent's instructions or system prompt give it a reason to reach for search (a model won't call a tool it doesn't know exists or doesn't think is relevant).

Calls fail with an auth error. Check bing_api_key is actually set somewhere - either on the node or in config.ini - and that it's a valid, active key. Bing's Search API is a paid Azure service past any free tier, so an expired key or exhausted quota fails the same way a missing one does.

You want a custom endpoint instead of Microsoft's default. That's what is_custom_api and custom_config_id are for - set is_custom_api true and point custom_config_id at whatever relay or alternate configuration you've set up, rather than fighting the node into using a URL field that doesn't exist here.