Skip to main content
Glama

pdf_metadata

Read or write PDF metadata, including title, author, subject, and keywords, to inspect or update document properties.

Instructions

Reads (or writes) metadata to a PDF. [Input: PDF (.pdf) | Output: PDF (.pdf)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "pdf_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
titleNoThe new title.
authorNoThe new author.
outputNoThe output PDF file path.
subjectNoThe new subject.
keywordsNoThe new keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it says nothing about overwrite behavior, whether an existing output file is replaced, whether writes require the output path, or what the read path returns. For a mutation-capable tool these omissions are significant.

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

Conciseness4/5

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

Two short, front-loaded sentences with a useful input/output type tag. Little is wasted, though the read/write hedge is a compression that sacrifices clarity rather than serving it.

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?

With six parameters, no annotations, and no output schema, the definition should explain mode selection, required-vs-optional interplay (input required, metadata optional), and the write result. None of that is present, so an agent could call it correctly only by inference.

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 description coverage is 100%, so per-parameter meaning is already handled by the schema's own one-liners, which sets the baseline at 3. The description adds nothing beyond that, and notably fails to explain the key semantic that the optional metadata parameters are what trigger write mode.

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

Purpose3/5

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

It names a resource (PDF metadata) and a verb, but the verb is a hedged 'Reads (or writes)', so the agent cannot tell whether this is a read or a mutation tool from the definition alone. 'Reads ... metadata to a PDF' is also grammatically muddled about direction of data flow.

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?

There is no statement of when to use this versus alternatives, and no explanation of the crucial condition that selects the read path versus the write path. Nothing indicates whether omitting output/supplying title switches modes, leaving the agent to guess.

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