Skip to main content
Glama

Update a knowledge hub

update_knowledge_hub
Destructive

Use this when the user wants to rename a knowledge hub or add websites and notes to it. New sites and notes are read in the background and the hub's pages follow. A website or note the hub already has is replaced by what is sent, and nothing is removed. A hub that is still being built is refused. Free.

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>"
    },
    "name": "update_knowledge_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA new name.
hubIdYesThe knowledge hub's id.
notesNo1 to 50 notes to add or replace, by `filename`. Nothing is removed.
websitesNo1 to 20 sites to add, or to read again when the hub has them. A site the hub has is replaced by what you send, so `includeSubPages` and `isCompetitor` left out become false. Nothing is removed.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag a non-read-only mutation, but the description adds genuinely new behavior: reads happen in the background, the hub's pages follow, existing sites/notes are replaced by what is sent, nothing is deleted, an in-progress hub is rejected, and the operation is free. That is exactly the kind of context an agent needs before calling a write tool with openWorldHint and destructiveHint set.

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 trigger condition is front-loaded in the first sentence, followed by effects, replacement semantics, the refusal case, and cost, with no padding or repetition. The terse 'Free.' sentence still carries a real constraint.

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 mutation tool with no output schema, the description covers when to call it, what gets changed, what gets overwritten, what gets rejected, and cost. Only the response shape and whether a hubId-only call is a no-op are left unaddressed, which are minor 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 coverage is 100%, including matching-by-filename and the default-false behavior of includeSubPages and isCompetitor, so the schema already does the heavy lifting. The description reinforces the replacement consequence for sites and notes but adds no format or constraint detail beyond what the schema states, which is the correct baseline-3 outcome.

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?

The description names a concrete verb and resource ('rename a knowledge hub or add websites and notes to it'), so the agent knows exactly what the tool mutates. It doesn't explicitly distinguish itself from page-level siblings like update_knowledge_hub_page, but the scope (hub name, sites, notes) is clear enough to separate it.

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?

'Use this when the user wants to rename a knowledge hub or add websites and notes to it' gives an explicit triggering condition, and 'A hub that is still being built is refused' adds a precondition. It stops short of naming an alternative tool for the cases this one refuses, but the when-to-use guidance is solid.

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