List docsbook docs
list_docsbook_docsREADno token needed$0.008 / callList EVERY page of Docsbook's own official documentation — the product's full table of contents. The one call that answers 'what can Docsbook do?' without having to guess a search query first: the page list is the feature list. Use it to orient yourself before advising a user what to do, to check whether a capability is documented at all, or when a search_docsbook_docs query came back empty and you need to know whether the topic is missing or just worded differently. 🔴 This is the PRODUCT's manual, not the user's documentation — that is get_doc_outline.
Optional: only pages under this prefix, e.g. 'guides/' or 'ai/'.
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_docsbook_docs",
"arguments": {}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_docsbook_docs","arguments":{}}}'Try it over REST#
The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.
Your workspace is resolved from the API key, so workspace_id is decided server-side here and anything you send for it is ignored.
/api/v1/list_docsbook_docsYour API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.
Optional: only pages under this prefix, e.g. 'guides/' or 'ai/'.
curl 'https://docsbook.io/api/v1/list_docsbook_docs' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY'