Skip to main content
Glama

Create Article

hudu_create_article

Create a new knowledge-base article in Hudu, storing HTML content that can be filed under a folder, scoped to a company, or left global.

Instructions

Create a new article in Hudu. An article is a knowledge-base document: HTML content, optionally filed in a folder and optionally scoped to one company. Articles with no company are global to the instance.

Returns the created record, including the id Hudu assigned. Hudu answers 422 with the offending field named when validation fails.

Operation class: Create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTitle of the article, shown in lists and search.
contentNoBody of the article, as HTML. Hudu stores this string and renders it as HTML in the knowledge base, so Markdown passed here is stored literally and shown to readers with its asterisks, hashes and pipes intact — convert to HTML (<h2>, <p>, <ul>, <table>, <a href="...">) before sending. Existing content is replaced wholesale on update, not appended to.
folder_idNoNumeric id of the folder to file the article under, from hudu_list_folders. Omit to leave the article at the top level. Pick a folder whose own company matches the article's — Hudu does not document what it does with a mismatch.
company_idNoNumeric id of the company whose knowledge base this article belongs to. Omit it to create a global article that is visible across every company. Resolve a customer name to an id with hudu_list_companies first.
enable_sharingNoPUBLISHES THIS ARTICLE TO THE PUBLIC INTERNET when set to true. Hudu mints a share URL (returned as `share_url` on the record) that renders the full article content to anyone holding the link, with no Hudu login, no company scoping and no record of who read it. Client documentation frequently contains internal hostnames, procedures and account references, so treat this as a disclosure decision rather than a formatting one: leave it unset unless the user has explicitly asked for a link they can send outside their Hudu tenant, and tell them what the article contains before you set it. Setting it to false withdraws an existing public URL.
Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds useful behavioral context: it returns the created record with the assigned id and explains that Hudu answers 422 with the offending field on validation failure. This adds value beyond what annotations provide.

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 concise and well-structured: it opens with the core purpose, defines the resource, and then provides operational details (return value, error handling) in a compact format. Every sentence adds value without unnecessary fluff.

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 description is complete enough for a create tool: it explains what the tool creates, the return value (including the assigned id), and validation error behavior. Since there is no output schema, this is necessary and provided. It does not mention additional details like HTML requirements, but those are covered in the input schema, so the description is sufficiently complete.

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%, and each parameter already has detailed descriptions (e.g., HTML content, folder_id, company_id, enable_sharing). The description itself does not add new parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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: 'Create a new article in Hudu' and distinguishes it from sibling tools like hudu_update_article and hudu_get_article by specifying the create operation. It also explains what an article is and the scoping options, making the tool's function unambiguous.

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 for when to use this tool (creating a knowledge-base article) and implies alternatives by mentioning scoping to company or global. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of the highest bar.

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/ZenixSolutions/hudu-mcp'

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