Skip to main content
Glama

Add a page to a hub

add_knowledge_hub_page

Use this when the user wants to add a page of their own to a knowledge hub, such as pricing notes or answers to common objections. Takes a title and the page in Markdown, up to 60,000 characters. Campaigns can draw on it at once. Free. Calling again adds a second page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hubId": "<hubId>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "add_knowledge_hub_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.
titleYesThe page's title.
contentYesThe page in Markdown, up to 60,000 characters.
categoryNoWhat the page is about. `custom` when left out.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write to a closed system. The description adds useful behavioral context beyond annotations: repeated calls create additional pages, campaigns can use the content immediately, and there is no cost. It still does not describe permissions, errors, or return value.

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 short and front-loaded with the trigger condition. Each sentence contributes either usage context, input expectations, or the important duplicate-page behavior.

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?

For a four-parameter write tool with complete schema coverage and no output schema, the description covers purpose, usage, and the non-idempotent duplicate behavior well. It could be more complete by mentioning the category option or what the call returns, but those are not severe omissions.

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 hubId, title, content, and category in detail, including the category default. The description repeats the title and Markdown content constraints but adds no additional meaning for hubId or category, so the baseline score of 3 applies.

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 states a specific verb and resource: add a page to a knowledge hub. It gives concrete examples of page content and clarifies that calling again adds a second page, which distinguishes this from an update operation.

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?

It clearly frames when to use the tool: when the user wants to add their own page to a hub. The note about repeat calls creating a second page warns against accidental duplication, but it does not explicitly name alternatives such as update_knowledge_hub_page for editing existing content.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources