Skip to main content
Glama

Search n8n Workflow Templates

search_templates
Read-onlyIdempotent

Search n8n workflow templates by keyword. Returns matching templates with nodes, description, and ID for fetching the full workflow JSON.

Instructions

Search n8n.io workflow templates by keyword.

Queries the official n8n template gallery API. Returns workflow templates that match the search query — each includes the nodes used, description, and a template ID for fetching the full workflow JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term (e.g. "slack message", "AI agent", "google sheets", "webhook", "email automation").
max_resultsNoMaximum templates to return (default 10, max 30).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds value by disclosing it queries an external API and specifying result contents (nodes, description, template ID).

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?

Two sentences with no wasted words. Purpose stated first, followed by relevant context and result details. Front-loaded and efficient.

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 low complexity (2 params, simple), 100% schema coverage, annotations that cover safety, and an output schema that defines return structure, the description is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds minor color (e.g., examples for query) but does not enhance understanding beyond schema defaults and constraints.

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?

Description clearly states 'Search n8n.io workflow templates by keyword' with specific verb and resource. Differentiates from siblings like get_template (single template retrieval) and search_docs (documentation search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States it queries the official n8n template gallery API, implying usage for finding templates. Does not explicitly mention when not to use or provide alternatives, though sibling names suggest distinctions.

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/okdk7788/docs-n8n-mcp'

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