Skip to main content
Glama
Sign In

Docstar

by io.github.swayammaheshwari
OverviewDiscussionsAdmin

list_collection_pages

Read-onlyIdempotent

Returns all non-deleted pages of a collection (the full sidebar tree, flat) with id, name, urlName, type, parentId, child (ordered child ids), state, isPublished, meta, sharingMeta and the endpoint requestType for endpoint pages. Page types: 0 invisible root, 1 parent page/module (top-level), 3 subpage, 4 API endpoint, 5 example/sample request of an endpoint. States: 0 pending, 1 draft, 2 approved/published, 3 rejected. Use it to find pageIds and the hierarchy. Collection must belong to the caller's org. GET https://api.docstar.io/orgs/:orgId/collection/:collectionId/pages

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": {
      "orgId": "<orgId>",
      "collectionId": "<collectionId>"
    },
    "name": "list_collection_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesThe orgId path variable
collectionIdYesThe collectionId path variable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, so the description's added value is the non-obvious behavioral detail: only non-deleted pages, returned as a flat tree, with the caller's org constraint. It stops short of describing ordering guarantees or error behavior, but adds real substance beyond the annotations.

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?

Front-loaded with the core action and scope, then the return fields, then the enum legends and the usage hint. The field enumeration is dense but earns its place since there is no output schema; the only waste is the URL string, which is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating returned fields, and it decodes the page-type and state enums an agent would otherwise have to guess at. Together with the org constraint, an agent has everything needed to call this correctly and interpret the result.

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% for the two path parameters, so the schema already does the work. The description only implicitly reinforces that collectionId must resolve to a collection owned by the caller's org; it adds no syntax or format detail beyond that.

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?

States a specific verb and resource ('Returns all non-deleted pages of a collection') and immediately characterizes the scope as the flat full sidebar tree. That distinguishes it clearly from siblings like list_collections (which lists collections, not pages) and create_page.

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 it to find pageIds and the hierarchy' gives a concrete reason to pick this tool, and the org-ownership prerequisite is stated. It does not name an alternative tool or say when not to use this, so it falls short of explicit routing guidance.

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

All Docstar toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources