Developer Tools

Tagged PDF Inspector

Compare StructTree-enabled and plain PDF extraction to see whether a document behaves like a tagged PDF and how much semantic structure it exposes

html· HTML resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/tagged-pdf-inspector' \
  -F 'file=@/path/to/pdfFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/tagged-pdf-inspector' \
  -F 'pdfFile=/public/samples/pdf/brand-guidelines-pdf-example1.pdf' \
  -F 'pages=' \
  -F 'includeHeaderFooter=false'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/tagged-pdf-inspector

Parameters

Name	Type	Required	Description
pdfFile	fileupload required	Yes	—
pages	text	No	—
includeHeaderFooter	checkbox	No	—

File-type parameters must be uploaded first via POST /upload/tagged-pdf-inspector, then the returned filePath is passed to the corresponding file field.

Response format

HTML result

JSON

{
  "result": "<div>Processed HTML content</div>",
  "error": "Error message (optional)",
  "message": "Notification message (optional)",
  "metadata": {
    "key": "value"
  }
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-tagged-pdf-inspector": {
      "name": "tagged-pdf-inspector",
      "description": "Compare StructTree-enabled and plain PDF extraction to see whether a document behaves like a tagged PDF and how much semantic structure it exposes",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=tagged-pdf-inspector",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "tagged-pdf-inspector",
    "arguments": {
  "pdfFile": "/public/samples/pdf/brand-guidelines-pdf-example1.pdf",
  "pages": "",
  "includeHeaderFooter": false
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

Browse tools Open tool