LlamaParse

Retrieve the full JSON Schema for one starter extraction template, by id, as returned by `searchSchemaTemplates`. Pass the schema to `createExtractionConfigFromSchema` — edit it first if the user needs extra or fewer fields.

Get a pre-signed URL to upload a file to the LlamaParse S3 storage

List the projects available to the user, with their names, so you can pass the right projectId to other tools. Use this whenever a tool needs a projectId and the correct project is not already known — pick by name, and ask the user if the name is ambiguous.

Grep the content of a file from an index, providing its file ID, the pattern to grep for and, optionally, a number of context characters and a maximum number of grep matches to retrieve

List the directories in a project. Returns one page at a time — pass the returned nextPageToken to fetch more. By default only user directories are listed; indexes create their own internal output directories, which are not valid sources for a new index.

List the files inside a directory, along with the directory itself. Returns one page at a time — pass the returned nextPageToken to fetch more. Use directoryFileId, not fileId, when referring to a file in later calls.

List all the available indexes on the LlamaParse Platform. Indexes are vector-indexed directories with the possibility of searching/reading/grepping files and performing retrieval.

Parse a file providing its file ID, retrieving markdown or plain text content of the file. Use with file IDs obtained with the getUploadUrl/uploadFileByUrl tool or that the user provided

Parse a PDF file with LiteParse, a fast, in-process parser that does not consume credits from the LlamaParse Platform. The tool needs a file ID obtained with the getUploadUrl/uploadFileByUrl tool or provided by the user. Only works with PDF files.

Read the content of a file from an index, providing its file ID and, optionally, an offset and a maximum length (in characters) to read.

Perform hybrid search on the index, providing a query and, optionally, the top K documents to retrieve and the top N documents to rerank

Search the built-in library of starter extraction schemas (invoice, contract, resume, 10-K, patient intake and more) by keyword or category. Returns matching templates with their top-level field names, but not the full JSON Schema — call `getSchemaTemplate` for that. Prefer this over `generateExtractionConfig` when the user wants a common document type: it is instant and needs no sample file.

Split a file into category-based segments providing its file ID. Use with file IDs obtained with the getUploadUrl/uploadFileByUrl tool or that the user provided

Re-index a directory, picking up files added or changed since the last run. Indexes do not refresh on their own, so this is the only way an existing index sees new documents. Runs in the background — poll getIndexStatus until status is ready. If a sync is already running, this returns syncStarted=false (the underlying API responds 409 or 429): do not retry syncIndex, call getIndexStatus to check the running sync and wait until status is ready.

Upload a file to LLamaParse S3 storage providing a URL to download the file data. On upload completion, the file will be sent to LlamaParse S3 storage, so that it can be used for downstream processing tasks like parsing, classification or splitting.