Skip to main content
Glama

n8n_get_tag

Retrieve a specific tag by its ID from the n8n workflow automation platform to organize and categorize workflow elements.

Instructions

Get a specific tag by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTag ID

Implementation Reference

  • The actual implementation of the getTag operation using the HTTP client.
    async getTag(id: string): Promise<any> {
      const response = await this.client.get(`/tags/${id}`);
      return response.data;
    }
  • The tool handler in the main server logic that calls n8nClient.getTag.
    case 'n8n_get_tag': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.getTag(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • src/index.ts:727-737 (registration)
    The registration of the n8n_get_tag tool with its input schema.
    {
      name: 'n8n_get_tag',
      description: 'Get a specific tag by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Tag ID' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only, there is no disclosure of error behavior (e.g., ID not found), authentication requirements, or what fields the returned tag contains.

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?

Extremely concise at six words. Front-loaded with verb and resource. No redundancy or wasted sentences for a single-parameter read operation.

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

Completeness3/5

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

Adequate for low-complexity tool with full schema coverage, but lacks description of return value structure or error states given the absence of an output schema. Does not define what a 'tag' represents in n8n context.

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 has 100% description coverage for the single 'id' parameter. The description mentions 'by ID' which aligns with the schema but adds no additional semantic value (format constraints, example IDs, or lookup behavior).

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

Purpose4/5

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

States clear verb+resource (Get + tag) and scope (specific by ID). The 'by ID' phrasing distinguishes from n8n_list_tags, but does not explicitly clarify relationship to n8n_get_workflow_tags or when to prefer listing over retrieval.

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

Usage Guidelines2/5

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

No guidance on when to use this versus n8n_list_tags (e.g., when the ID is already known) or n8n_get_workflow_tags. No mention of prerequisite steps like obtaining the tag ID.

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/Shravan1610/n8n-mcp-server'

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