Skip to main content
Glama
pablontiv

PDF Reader MCP Server

by pablontiv

extract_pdf_metadata

Extract metadata and document information from PDF files to analyze file properties and content structure.

Instructions

Extract metadata and document information from PDF files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the PDF file to extract metadata from

Implementation Reference

  • The main handler function for the 'extract_pdf_metadata' tool. It validates input using Zod schema, instantiates MetadataParser, and calls parseMetadata on the provided file path.
    export async function handleExtractMetadata(args: unknown): Promise<PDFMetadata> {
      try {
        const params = ExtractMetadataParamsSchema.parse(args);
        const parser = new MetadataParser();
        
        return await parser.parseMetadata(params.file_path);
      } catch (error) {
        const mcpError = handleError(error, typeof args === 'object' && args !== null && 'file_path' in args ? String(args.file_path) : undefined);
        throw new Error(JSON.stringify(mcpError));
      }
    }
  • Zod schema used for input validation in the tool handler, defining the required 'file_path' parameter.
    export const ExtractMetadataParamsSchema = z.object({
      file_path: filePathValidation
    });
  • src/index.ts:63-71 (registration)
    Switch case registration in the main server request handler that dispatches calls to 'extract_pdf_metadata' to the handleExtractMetadata function.
    case 'extract_pdf_metadata':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await handleExtractMetadata(args), null, 2),
          },
        ],
      };
  • src/index.ts:41-44 (registration)
    Tool listing registration where extractMetadataTool is included in the list returned for ListToolsRequestSchema.
    extractTextTool,
    extractMetadataTool,
    extractPagesTool,
    validatePDFTool,
  • Core helper method that performs the actual PDF metadata extraction using pdf-parse library, including file validation, reading, parsing, and formatting.
    async parseMetadata(filePath: string): Promise<PDFMetadata> {
      await validatePDFFile(filePath);
      
      const buffer = await fs.readFile(filePath);
      const stats = await fs.stat(filePath);
      
      const pdfData = await withTimeout(
        pdf(buffer),
        this.config.processingTimeout
      );
    
      return this.formatMetadata(pdfData, stats.size);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions extraction but doesn't describe what metadata is returned (e.g., author, creation date, page count), whether the operation is read-only or has side effects, error handling, or performance characteristics. This leaves significant gaps for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what metadata is extracted, the return format, or potential limitations (e.g., encrypted PDFs). For a tool with no structured behavioral or output information, more detail is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the single parameter 'file_path' clearly documented. The description adds no additional parameter details beyond what the schema provides, such as file format requirements or path validation rules. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('extract') and resource ('metadata and document information from PDF files'). It distinguishes from siblings like 'extract_pdf_text' (which extracts text content) and 'extract_pdf_pages' (which extracts pages), but doesn't explicitly mention these distinctions in the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'extract_pdf_text' or 'validate_pdf'. It states what the tool does but offers no context about use cases, prerequisites, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pablontiv/pdf-reader-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server