Skip to main content
Glama
WOOWTECH

Woow n8n MCP Server

by WOOWTECH

search_templates

Read-onlyIdempotent

Search n8n workflow templates by keyword, node types, task, metadata, or pattern summaries to find the right automation blueprint.

Instructions

Search templates with multiple modes. Use searchMode='keyword' for text search, 'by_nodes' to find templates using specific nodes, 'by_task' for curated task-based templates, 'by_metadata' for filtering by complexity/setup time/services, 'patterns' for lightweight workflow pattern summaries mined from 2700+ templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNoFor searchMode=by_task: the type of task. For searchMode=patterns: optional category filter (omit for overview of all categories).
limitNoMaximum number of results. Default 20.
queryNoFor searchMode=keyword: search keyword (e.g., "chatbot")
fieldsNoFor searchMode=keyword: fields to include in response. Default: all fields.
offsetNoPagination offset. Default 0.
categoryNoFor searchMode=by_metadata: filter by category (e.g., "automation", "integration")
nodeTypesNoFor searchMode=by_nodes: array of node types (e.g., ["n8n-nodes-base.httpRequest", "n8n-nodes-base.slack"])
complexityNoFor searchMode=by_metadata: filter by complexity level
searchModeNoSearch mode. keyword=text search (default), by_nodes=find by node types, by_task=curated task templates, by_metadata=filter by complexity/services, patterns=lightweight workflow pattern summarieskeyword
targetAudienceNoFor searchMode=by_metadata: filter by target audience (e.g., "developers", "marketers")
maxSetupMinutesNoFor searchMode=by_metadata: maximum setup time in minutes
minSetupMinutesNoFor searchMode=by_metadata: minimum setup time in minutes
requiredServiceNoFor searchMode=by_metadata: filter by required service (e.g., "openai", "slack")
Behavior4/5

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

Annotations provide readOnlyHint and idempotentHint, and the description aligns with them. The description adds context about the patterns mode ('lightweight workflow pattern summaries mined from 2700+ templates') and the multi-mode behavior, going beyond the structured annotations.

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?

The description is only two sentences, front-loaded with the verb and resource. The second sentence efficiently lists all five modes with their use cases, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (13 params, 5 modes, no output schema), but the schema covers parameter details. The description gives enough context to choose a mode and understand the tool's scope, though it could explicitly mention mode-specific parameter requirements or response format.

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 description coverage is 100%, so baseline is 3. The description mirrors the searchMode enum descriptions from the schema and adds only the '2700+ templates' detail. It does not provide additional meaning for other parameters like query, nodeTypes, or limit beyond what the schema already has.

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?

The description clearly states the tool's purpose: 'Search templates with multiple modes.' It distinguishes itself from siblings like get_template (retrieval) and search_nodes (node search) by explicitly targeting templates and enumerating all five search modes.

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?

It provides explicit mode-specific usage guidance (keyword for text search, by_nodes for specific nodes, etc.), which helps the agent select the right mode. However, it does not mention when to prefer alternative tools like get_template for direct retrieval.

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/WOOWTECH/woow_n8n_mcp_server'

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