Skip to main content
Glama

n8n_get_credential_schema

Retrieve the schema for a specific credential type to understand required fields and structure for authentication setup.

Instructions

Get the schema for a credential type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credentialTypeNameYesCredential type name

Implementation Reference

  • The actual implementation of the credential schema retrieval logic in the n8n client.
    async getCredentialSchema(credentialTypeName: string): Promise<any> {
      const response = await this.client.get(`/credentials/schema/${credentialTypeName}`);
      return response.data;
    }
  • src/index.ts:637-645 (registration)
    Registration of the n8n_get_credential_schema tool and its input schema.
    {
      name: 'n8n_get_credential_schema',
      description: 'Get the schema for a credential type',
      inputSchema: {
        type: 'object',
        properties: {
          credentialTypeName: { type: 'string', description: 'Credential type name' },
        },
        required: ['credentialTypeName'],
  • Handler logic for n8n_get_credential_schema in the tool execution switch statement.
    case 'n8n_get_credential_schema': {
      if (!args?.credentialTypeName) throw new Error('credentialTypeName is required');
      const result = await n8nClient.getCredentialSchema(args.credentialTypeName as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. 'Get' implies read-only, but lacks disclosure of return format, authentication requirements, or whether schema is static/dynamic. No mention of what happens if credential type doesn't exist.

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?

Single sentence with no waste. However, extreme brevity leaves gaps for a tool lacking annotations and output schema. Information density is high but insufficient for complete understanding.

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

Completeness2/5

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

Lacks explanation of return value structure despite no output schema being defined. No mention of available credential types or relationship to n8n_create_credential. Given zero annotations, description should compensate with richer behavioral 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 (parameter described as 'Credential type name'), meeting baseline. Description adds no additional semantic value about valid credential type values or format constraints beyond schema.

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?

Clear verb 'Get' with specific resource 'schema for a credential type'. Distinguishes from credential instance operations (like create_credential) by specifying 'schema', though could better differentiate from credential management tools.

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 sibling tools. Missing context such as 'use before create_credential to validate required fields' or indication of how credentialTypeName values are discovered.

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