Skip to main content
Glama

Search Node-RED nodes

nodered_search_nodes
Read-onlyIdempotent

Find Node-RED nodes by type or name across all flows and subflows, returning each match's flow, label, and disabled state without changing anything.

Instructions

Find Node-RED nodes by type and/or name across all flows and subflows.

Reads GET /flows and matches every node except tab and subflow definitions: type and name are case-insensitive substrings, both must match when both are given. Each hit carries its flow (or subflow) id and label and whether it is disabled (node or flow). Changes nothing.

Use when: locating nodes of one kind, e.g. every api-call-service or server-state-changed node, or a node by its name. Not for: which nodes use one HA entity — use nodered_find_entity_usage; a whole flow — use nodered_get_flow. Returns: {"addon_slug", "rev", "matches": [{id, type, name, flow_id, flow_label, in_subflow, disabled, config?}], "count", "truncated"}; config only with include_config, plus redacted_fields then. Errors: no_filter when neither type nor name is given (no I/O), plus the add-on lookup errors of nodered_list_flows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nodered_search_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCase-insensitive part of the node's name as shown in the editor.
typeNoCase-insensitive part of the node type, e.g. `api-call-service`, `mqtt in`, `function`.
limitNoMaximum number of nodes returned (1-500, default 100).
flow_idNoOnly nodes in this flow (tab) or subflow id; omit to search everywhere.
include_configNoTrue adds each node's full configuration (secrets replaced by the placeholder).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.29.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description adds real value beyond them: it reveals the underlying `GET /flows` read, the exclusion of tab/subflow definitions, the substring-matching rule, the disabled flag per hit, and that nothing is changed. It also discloses the `no_filter` error and that it occurs before any I/O, which an agent needs to avoid a wasted call.

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?

Front-loaded with the one-line purpose, then segmented into reading behavior, "Use when", "Not for", "Returns", and "Errors". Dense but every line carries information an agent needs; there is no filler or restatement of the name.

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?

Covers the full decision surface for a search tool: match semantics, scope, what each hit contains, truncation, and error conditions. The return shape is repeated despite an output schema existing, which is mild redundancy but reinforces the redaction coupling rather than harming completeness.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: when both `type` and `name` are supplied, both must match (an AND-combination rule not stated in the schema). It also clarifies that `config` appears only with `include_config` and that `redacted_fields` accompanies it, adding meaning beyond the property 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?

States a specific verb and resource plus scope: "Find Node-RED nodes by type and/or name across all flows and subflows." It also explicitly excludes tab and subflow definition nodes, so the agent knows the match set precisely and can tell it apart from nodered_get_flow and nodered_find_entity_usage.

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?

Contains an explicit "Use when" clause with concrete examples (`api-call-service`, `server-state-changed`, or lookup by name) and a "Not for" clause that routes to the correct sibling for entity usage and whole-flow retrieval. Both the selection and the exclusions are named, leaving nothing to inference.

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

Deploy Server

Other Tools