Skip to main content
Glama

List a hub's pages

list_knowledge_hub_pages
Read-only

Use this when the user wants to read what a knowledge hub says. Returns the hub's pages with their content in Markdown, and whether each was written from the hub's sources, edited since, or added by hand. Pages can be long. 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": "list_knowledge_hub_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.

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 declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the description adds value by disclosing the return shape (Markdown page bodies with provenance flags), a size caveat ('Pages can be long'), and a cost signal ('Free'). It does not mention ordering, truncation limits or whether page ids are returned for follow-up mutations, which would matter for chaining into update/regenerate page tools.

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 with the usage trigger front-loaded, followed by return contents, size caveat and cost. Every sentence carries information; the only mild inefficiency is that purpose is folded into the usage clause rather than stated first.

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 single-parameter read tool with annotations and no output schema, the description covers what comes back and its shape well enough to call correctly. The remaining gap is whether the returned pages carry identifiers needed to invoke update_knowledge_hub_page or regenerate_knowledge_hub_page, which is not stated.

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?

Only one parameter (hubId) and the schema description coverage is 100%, so the schema fully documents the 24-char hex id constraint. The description adds no meaning about the id beyond that, 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?

States a specific verb and resource ('Returns the hub's pages') and adds what the payload contains: Markdown content plus per-page provenance (written from sources, edited since, added by hand). It does not explicitly differentiate itself from get_knowledge_hub or the page-level siblings, so it is clear but not sibling-differentiating.

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 read what a knowledge hub says' gives an explicit triggering condition, which is more than most list tools offer. There is no when-not guidance or named alternative (e.g. use get_knowledge_hub for metadata only), so it stops short of full routing guidance.

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