Skip to main content
Glama

get_pdf_metadata

Retrieve the title, author, creation date, and other metadata from a PDF file by providing its absolute path.

Instructions

Extract metadata information from a PDF file (title, author, creation date, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the PDF file

Implementation Reference

  • src/index.ts:42-55 (registration)
    Tool registration: defines the 'get_pdf_metadata' tool with name, description, and inputSchema (accepts filePath).
    {
      name: 'get_pdf_metadata',
      description: 'Extract metadata information from a PDF file (title, author, creation date, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          filePath: {
            type: 'string',
            description: 'Absolute path to the PDF file',
          },
        },
        required: ['filePath'],
      },
    },
  • Tool handler: when 'get_pdf_metadata' is called, it extracts filePath, calls extractMetadata(filePath), and returns the metadata as JSON.
    case 'get_pdf_metadata': {
      const { filePath } = args as { filePath: string };
      const metadata = await extractMetadata(filePath);
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(metadata, null, 2),
          },
        ],
      };
    }
  • The actual implementation: extractMetadata() reads the PDF file, parses it with PDFParse, extracts metadata (title, author, subject, creator, producer, creationDate, modificationDate, keywords, totalPages), and returns it.
    export async function extractMetadata(filePath: string): Promise<PDFMetadata> {
      try {
        const dataBuffer = await fs.readFile(filePath);
        const parser = new PDFParse({ data: dataBuffer });
        const result = await parser.getInfo();
        await parser.destroy();
    
        return {
          title: result.info?.Title,
          author: result.info?.Author,
          subject: result.info?.Subject,
          creator: result.info?.Creator,
          producer: result.info?.Producer,
          creationDate: result.info?.CreationDate,
          modificationDate: result.info?.ModDate,
          keywords: result.info?.Keywords,
          totalPages: result.total,
        };
      } catch (error) {
        throw new Error(`Failed to extract metadata: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Type definition: PDFMetadata interface defines the shape of the metadata returned by the tool.
    export interface PDFMetadata {
      title?: string;
      author?: string;
      subject?: string;
      creator?: string;
      producer?: string;
      creationDate?: string;
      modificationDate?: string;
      keywords?: string;
      totalPages?: number;
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose safety properties (e.g., read-only nature), error handling for missing files, or permissions required. The description carries the full behavioral disclosure burden but provides only a high-level summary.

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 concise sentence that front-loads the core action ('Extract metadata information'). Every word carries meaning with no fluff or redundancy, earning a top score.

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

Completeness3/5

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

The description is adequate for a simple metadata extraction tool but lacks details on return format (no output schema) and does not address limitations or variations. It covers the basic purpose but leaves some gaps for an AI agent.

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?

Schema coverage is 100% since 'filePath' is fully described in the input schema. The description adds no additional parameter-level context beyond what the schema already provides. Baseline score of 3 applies, as the description does not reduce clarity.

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

Purpose5/5

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

The description clearly states 'Extract metadata information from a PDF file' with specific metadata fields listed (title, author, creation date). This verb+resource combination is distinct from sibling tools like 'extract_pdf_image' or 'read_pdf', making the tool's purpose immediately clear.

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 its siblings (e.g., get_pdf_page_count, search_pdf). An agent would not know that this tool is for metadata only, not content or images, without additional context.

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/rturv/mcp-pdf-reader'

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