Tools reference Leave feedback
On this page
Complete reference of every tool the GroupDocs.Parser MCP server exposes to AI agents, with parameters, example prompts, and results. Captured from a live tools/list call against server version 26.9.0 (raw capture: tools-list.generated.json in this section’s source).
| Tool | What it does |
|---|---|
extract_text | Extracts plain text from a document, whole or a single page |
extract_tables | Extracts tables as Markdown (renders in chat) or structured JSON |
extract_metadata | Extracts author, title, dates, custom properties, EXIF, XMP, IPTC as JSON |
extract_images | Extracts embedded images and saves them to storage as files |
extract_barcodes | Decodes barcodes and QR codes, returning values, types, and positions |
get_document_info | Returns file type, page count, and size without extracting anything |
get_license_status | Reports the active licensing mode and, under metered licensing, consumption |
Every tool takes its document through the same file object — pass either a name from your storage folder or inline content:
{ "file": { "filePath": "invoice.pdf" } }
| Field | Type | Description |
|---|---|---|
filePath | string | File path or name in the configured storage folder |
fileContent | string | Base64-encoded file content (alternative to filePath) |
fileName | string | Original filename with extension — required with fileContent. Since 26.9.0 it also works on its own, resolved from the storage folder exactly like filePath |
You rarely write this JSON yourself: the AI agent does, from your plain-language prompt. Missing files are not an error to fear — the tool responds with the list of available files so the agent can correct itself.
- extract_text
- extract_tables
- extract_metadata
- extract_images
- extract_barcodes
- get_document_info
- get_license_status
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.
