> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/knowledge-base-access/read-knowledge-base-file.md).

# Read Knowledge Base File

Retrieve the parsed text of a known file in a knowledge base. Use it when you need to read a specific document rather than search for relevant passages.

## Use this tool

1. Select the **Knowledge Base** containing the file.
2. Enter the exact **File Path** from [List Knowledge Base Contents](https://docs.stackai.com/stackai-tools/knowledge-base-access/list-knowledge-base-contents.md).
3. Set **Max Length** to control how much text is returned.
4. Run the tool. Review **File Content**, **Content Length**, and **Citation ID**.

## Behavior and limits

Max Length is measured in characters and defaults to 50,000. A long file can be truncated. The output is parsed text rather than the original downloadable file. Enable the knowledge base permission setting when the signed-in user must have access to the selected base.

## Inputs

| Field                | Parameter   | Description                                                      |
| -------------------- | ----------- | ---------------------------------------------------------------- |
| File Path (required) | `file_path` | The absolute path to the file to read within the knowledge base. |

## Configuration

| Field                                      | Parameter                    | Description                                                                                      |
| ------------------------------------------ | ---------------------------- | ------------------------------------------------------------------------------------------------ |
| Max Length                                 | `max_length`                 | Maximum number of characters to return from the file content. Default: `50000`.                  |
| Knowledge Base (required)                  | `selected_kb_items`          | The knowledge base containing the file to read.                                                  |
| Enforce StackAI knowledge base permissions | `enforce_end_user_kb_access` | Require the end user to hold a role on the knowledge base containing the file. Default: `false`. |

## Outputs

| Field          | Parameter        | Description                                                      |
| -------------- | ---------------- | ---------------------------------------------------------------- |
| File Path      | `file_path`      | The path of the file that was read                               |
| File Content   | `file_content`   | The parsed text content of the file                              |
| File Type      | `file_type`      | The type/format of the file                                      |
| Content Length | `content_length` | The actual length of the returned content in characters          |
| Citation ID    | `citation_id`    | The unique citation identifier for this file (e.g., '23183.0.0') |

## Related guides

* [Retrieval Settings and Result Ranking](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/retrieval-settings-and-result-ranking.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/knowledge-base-access/read-knowledge-base-file.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
