Skip to main content
Glama

pylon_create_knowledge_base_article

Add new documentation, FAQs, or troubleshooting guides to a knowledge base for customer self-service support.

Instructions

Create a new help article in a knowledge base. Use this to add new documentation, FAQs, or troubleshooting guides that customers can access for self-service support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
knowledge_base_idYesID of the knowledge base to add article to. Example: "kb_123abc"
titleYesArticle title that clearly describes the topic. Examples: "How to Reset Your Password", "Troubleshooting Login Issues", "Billing FAQ"
contentYesFull article content in markdown or HTML format. Include step-by-step instructions, screenshots, and links. Example: "## Steps to Reset Password 1. Go to login page 2. Click Forgot Password..."

Implementation Reference

  • Handler for the 'pylon_create_knowledge_base_article' tool. Validates required parameters (knowledge_base_id, title, content), calls the PylonClient.createKnowledgeBaseArticle method, and returns the created article as JSON.
    case 'pylon_create_knowledge_base_article': {
      if (!args || !('knowledge_base_id' in args) || !('title' in args) || !('content' in args)) {
        throw new Error('knowledge_base_id, title, and content are required');
      }
      const article = await pylonClient.createKnowledgeBaseArticle(
        args.knowledge_base_id as string,
        { title: args.title as string, content: args.content as string }
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(article, null, 2),
          },
        ],
      };
    }
  • Tool registration schema defining the 'pylon_create_knowledge_base_article' tool with its name, description, and input validation schema. Specifies three required parameters: knowledge_base_id, title, and content.
      name: 'pylon_create_knowledge_base_article',
      description: 'Create a new help article in a knowledge base. Use this to add new documentation, FAQs, or troubleshooting guides that customers can access for self-service support.',
      inputSchema: {
        type: 'object',
        properties: {
          knowledge_base_id: { type: 'string', description: 'ID of the knowledge base to add article to. Example: "kb_123abc"' },
          title: { type: 'string', description: 'Article title that clearly describes the topic. Examples: "How to Reset Your Password", "Troubleshooting Login Issues", "Billing FAQ"' },
          content: { type: 'string', description: 'Full article content in markdown or HTML format. Include step-by-step instructions, screenshots, and links. Example: "## Steps to Reset Password\n1. Go to login page\n2. Click Forgot Password..."' },
        },
        required: ['knowledge_base_id', 'title', 'content'],
      },
    },
  • PylonClient method that makes the actual HTTP POST request to create a knowledge base article. Takes a knowledge base ID and article object (title, content), sends to the Pylon API endpoint, and returns the created article.
    async createKnowledgeBaseArticle(knowledgeBaseId: string, article: Omit<PylonArticle, 'id' | 'knowledge_base_id'>): Promise<PylonArticle> {
      const response: AxiosResponse<PylonArticle> = await this.client.post(`/knowledge-bases/${knowledgeBaseId}/articles`, article);
      return response.data;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it indicates this is a creation tool, it lacks details on permissions required, whether the article is published immediately, rate limits, error handling, or what happens on success (e.g., returns an article ID). This is a significant gap for a mutation tool with zero annotation coverage.

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 two sentences, front-loaded with the core purpose and followed by usage context. Every sentence earns its place with no wasted words, making it efficient and well-structured for quick understanding.

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?

Given that this is a mutation tool with no annotations and no output schema, the description is incomplete. It covers the purpose and usage context adequately but lacks behavioral details (e.g., side effects, response format) and does not compensate for the absence of structured fields, leaving gaps for an AI agent to invoke it correctly.

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 the schema already documents all three parameters thoroughly. The description does not add any additional meaning or context beyond what the schema provides (e.g., it doesn't explain parameter interdependencies or usage tips). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Create') and resource ('new help article in a knowledge base'), distinguishing it from siblings like pylon_create_contact or pylon_create_issue. It specifies the purpose is for adding documentation, FAQs, or troubleshooting guides for customer self-service support, making it highly specific and differentiated.

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?

The description provides clear context on when to use this tool ('to add new documentation, FAQs, or troubleshooting guides that customers can access for self-service support'), but it does not explicitly mention when not to use it or name alternatives. For example, it doesn't compare to pylon_create_issue for support tickets or pylon_get_knowledge_base_articles for 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/marcinwyszynski/pylon-mcp'

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