Skip to main content
Glama

pdf_bookmarks

Extract and update bookmarks in PDF files, returning them as a structured JSON array for navigation or indexing.

Instructions

Handles bookmarks in a PDF. [Input: PDF (.pdf) | Output: JSON array]

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>",
      "output": "<output>"
    },
    "name": "pdf_bookmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output PDF file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: not whether the PDF is mutated, whether existing bookmarks are replaced, or what permissions are needed. Worse, "Output: JSON array" conflicts with the schema's required 'output' PDF file path, leaving the mutation/return behavior genuinely ambiguous.

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

Conciseness3/5

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

The definition is very short with no padding, and the input/output bracket is front-loaded. However, that brevity comes at the cost of under-specification, and the bracket notation is ambiguous rather than informative.

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?

For a two-parameter tool with no annotations and no output schema, the description should explain the operation, its effect on the PDF, and the return value. Instead it omits all of that and leaves an unresolved inconsistency between the stated JSON-array output and the required output PDF path.

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 both parameters are documented in the schema itself and the baseline of 3 applies. The description mentions input and output types but adds no meaning beyond them, and its JSON-array output claim muddies rather than clarifies the 'output' parameter.

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

Purpose2/5

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

"Handles bookmarks in a PDF" names the resource but the verb is vague: it is unclear whether the tool lists, extracts, adds, edits, or deletes bookmarks. The bracketed I/O note suggests a read that returns a JSON array, yet the schema requires an output PDF path, so an agent cannot confidently predict what the tool does.

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?

No when-to-use guidance, prerequisites, or alternatives are given, despite many sibling tools (pdf_annotate, pdf_extract_text, etc.) that could plausibly overlap. The agent must guess whether this belongs in a bookmark-inspection workflow or a bookmark-editing one.

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