Skip to main content
Glama

Update a hub's page

update_knowledge_hub_page
DestructiveIdempotent

Use this when the user wants to change a knowledge hub page's title or content. New content replaces the page's whole content. A page written from the hub's sources becomes edited, and is still rewritten when its sources change. 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>",
      "pageId": "<pageId>"
    },
    "name": "update_knowledge_hub_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.
titleNoA new title.
pageIdYesThe page's id, as the hub's pages list gives it.
contentNoNew Markdown, up to 60,000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description earns credit by explaining the actual destruction semantics: new content replaces the whole page content, and a source-derived page becomes hand-edited yet still gets rewritten on source changes. It also discloses cost ('Free'), which annotations cannot convey. It does not mention permissions or what the response returns, but with annotations covering the safety profile this is solidly above baseline.

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?

Four short sentences, front-loaded with the triggering condition, then overwrite behavior, then the source-rewrite side effect, then cost. Nothing is padded, though the source/rewrite sentence is slightly dense and could be read as ambiguous about which tool performs the rewrite.

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 4-parameter mutation with no output schema, the description covers the two things an agent most needs beyond the schema: partial-vs-full content replacement and the surprising interaction with source-driven regeneration. Authentication requirements and the return shape are absent, but the schema and annotations carry most of the remaining burden.

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 hubId, pageId, title and content are already documented, including the id-source hint for pageId and the 60,000-character Markdown limit. The description only restates that title and content are the mutable fields and adds no format or partial-update semantics beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('change a knowledge hub page's title or content') and names the two mutable fields, so an agent can tell this is an in-place edit of an existing page rather than an add/regenerate/delete. It stops short of explicitly contrasting itself with the sibling tools like regenerate_knowledge_hub_page, so it lands at 4 rather than 5.

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 opening clause 'Use this when the user wants to change a knowledge hub page's title or content' is a clear triggering condition. There is no when-not guidance and no named alternative (e.g. use regenerate when you want sources re-synthesized), which keeps it below 5.

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