​

list_knowledge_documents

​

Use Cases

• Discover what documents and webpages are in the knowledge base
• Build a catalog or browser UI for project knowledge
• Get exact document names to pass to get_document_full_content
• Verify that knowledge sources are available before searching

​

Parameters

​

Response

​

Example Request

{}

​

Example Response

{
  "success": true,
  "documents": [
    {
      "name": "Product Guide.pdf",
      "type": "document",
      "id": "doc_abc123"
    },
    {
      "name": "API Documentation",
      "type": "webpage",
      "id": "web_xyz",
      "url": "https://example.com/api-docs"
    }
  ],
  "summary": "I have access to 2 knowledge source(s):\n\nDocuments (1):\n  - Product Guide.pdf\n\nWebpages (1):\n  - API Documentation (https://example.com/api-docs)",
  "count": 2
}

​

Behavior

• Returns all documents and webpages in the project (no agent scoping)
• Document names are suitable for passing to get_document_full_content
• Empty knowledge base returns an empty documents array and count: 0

​

Error Handling

​

Best Practices

1. Call before get_document_full_content: Use the returned name values exactly when calling get_document_full_content
2. Cache sparingly: List can change as new documents are added; refresh when building UIs or after uploads
3. Combine with search: Use list_knowledge_documents to see what exists; use search_knowledge for semantic queries

​

Related Tools

• search_knowledge: Search the knowledge base with a query
• get_document_full_content: Retrieve the full text of a document by name