n8n Management MCP Server

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

Annotations already indicate read-only, non-destructive, and open-world behavior. The description adds valuable context by specifying the return format ('tag ID and name') and the optional limit parameter's effect ('default: all'), which clarifies retrieval behavior beyond the annotations. No contradictions with annotations are present.

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

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

The description is two sentences that are front-loaded with the core purpose and efficiently convey usage guidelines. Every sentence adds value without redundancy, making it appropriately sized and well-structured for quick comprehension.

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

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

Given the tool's low complexity (one optional parameter), rich annotations (read-only, non-destructive, open-world), and no output schema, the description is largely complete. It covers purpose, usage, and return format, though it could briefly mention pagination or ordering for the list, but this is minor given the context.

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

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

The input schema has 100% description coverage, with the 'limit' parameter fully documented in the schema itself. The description does not add any parameter-specific details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieve all available tags') and resource ('tags for workflow organization'), distinguishing it from sibling tools like n8n_get_tag (singular) and n8n_get_workflow_tags (tags for a specific workflow). It explicitly mentions the return format ('tag ID and name'), making the purpose unambiguous.

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

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

The description provides explicit guidance on when to use this tool: 'Use this before assigning tags to workflows or to see your tagging structure.' This clearly indicates the intended context (pre-assignment or structural review) and implicitly distinguishes it from alternatives like n8n_get_tag (for specific tags) or n8n_get_workflow_tags (for tags on workflows).

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