Skip to main content
Glama

search_flows

Read-only

Find every flow and block whose contents contain a keyword. Read-only. Searches message text and its translations, button labels and URLs, action names and configs, action input/output field paths and values, condition operands, trigger commands and payloads, custom-code files, and flow names and descriptions. A keyword matching a VARIABLE NAME also returns the blocks that reference that variable, which plain text search cannot do because blocks store variable ids, not names. truncated is true whenever a limit dropped something, and cappedBy names which: FLOW_LIMIT (more flows matched than limit), ROW_LIMIT (the 1000-match ceiling was hit; lower-ranked matches were not read), MATCHED_VARIABLES (the keyword matched more than 25 variable names — only the 25 closest, shortest name first, are resolved to the blocks that reference them, so blocks reading the others are MISSING), MATCHES_PER_FLOW (a flow lists at most 12 matches; its matchCount is the real number), MATCHES_PER_BLOCK (a block lists at most 3). A truncated answer is not proof that nothing else matches: narrow the keyword, or search the full variable name, before you rename or remove something on the strength of it. Use this instead of walking flows with get_flow_context when you know what the content says but not where it lives. Broadcast-backed flows and operation graphs are excluded — use list_broadcasts and the operations tools for those.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum flows to return. Defaults to 30; values above 100 are clamped to 100. Check `truncated` and `cappedBy`: this is only one of the limits that can cut the answer.
queryYesRequired. Case-insensitive substring, at least 2 characters. Matched against text, not tokenised — search a distinctive phrase or a variable name rather than a single common word.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum flows to return. Defaults to 30; values above 100 are clamped to 100. Check `truncated` to detect a cut-off result set."New value: +"Maximum flows to return. Defaults to 30; values above 100 are clamped to 100. Check `truncated` and `cappedBy`: this is only one of the limits that can cut the answer."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile, so this is beyond the bar: the description explains the undocumented variable-name matching behavior, names each truncation cause (FLOW_LIMIT, ROW_LIMIT, MATCHED_VARIABLES, MATCHES_PER_FLOW, MATCHES_PER_BLOCK) and what it means for completeness, and warns that a truncated answer is not proof of absence before a rename/delete.

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

Conciseness4/5

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

Purpose and routing are front-loaded in the first two sentences, and the truncation catalogue is genuinely load-bearing for interpreting results. It is still long, and the sentence about `truncated`/`cappedBy` restates material already present in the `limit` schema description, which is the main redundancy.

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?

With no output schema, the description carries return-value semantics itself — truncated, cappedBy, matchCount, the 12/3 match caps, the 1000-row ceiling, and the 25-variable resolution cap — plus scope exclusions. An agent has everything needed to call it and to judge result 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; the description adds real meaning about the query parameter by explaining that variable-name matches resolve to referencing blocks and that truncated/cappedBy interplay means limit is only one of several cutting limits. That said, much of the limit/truncation text duplicates what the schema's own `limit` description already says.

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 ('Find every flow and block whose contents contain a keyword') and immediately scopes it ('read-only'). It also enumerates exactly what surfaces are searched and explicitly names the sibling it replaces (get_flow_context) and the ones it defers to (list_broadcasts, operations tools).

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?

Gives an explicit routing rule: 'Use this instead of walking flows with get_flow_context when you know what the content says but not where it lives.' It also states exclusions (broadcast-backed flows, operation graphs) and points to the alternatives for those cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.