Get repository file tree
Returns a bounded directory tree for one repository, with short generated summaries for files and folders. Use it for structural orientation when you need to see how a repository (or one directory) is laid out; bound the response with max_depth and max_nodes. For concept questions prefer semantic_search — a folder whose name matches a concept is one candidate, not the whole story.
Authorizations
API Key authentication using Bearer token. Example: "Authorization: Bearer {apiKey}"
Body
Optional success projection. Omit to return both obj and rendered; use json for obj only; use agentic for rendered text only. Repairable errors always return both obj.error and rendered.
json, agentic One repository name or id returned by get_data_sources. Required when more than one repository is visible.
Optional repository-relative directory path. Omit for repository root.
Optional traversal depth limit.
Optional maximum number of tree nodes to return.
Optional rendered output depth limit.
Response
Success envelope. obj contains trees[] (one per resolved repository) with a rendered tree string and a hint; rendered is the JSON-serialized form of obj. Repairable failures (missing or invalid arguments, ambiguous or unknown data sources) also return HTTP 200 with obj.error = { code, message, retry, try } and a rendered <tool_error> block; repair the arguments and retry.