Skip to main content
Glama

Convert PDF to Word

pdf_to_word
Idempotent

Turn your PDFs into editable Word documents that look just like the original: same fonts, margins, tables, columns and images. Returns a link to download the result (kept about an hour). Credits on paid plans: 10 per file + 1 per page (at most 50 per file).

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": {
      "files": "<files>"
    },
    "name": "pdf_to_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=true), and the description goes beyond them with genuinely useful operational facts: the result is delivered as a download link, that link expires in about an hour, and the credit cost formula is 10 per file plus 1 per page capped at 50 per file. What is missing is failure behavior (bad URLs, oversized files, encrypted PDFs) and whether the conversion is synchronous.

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?

Two sentences with no filler: the first defines the output and its fidelity, the second front-loads the return value and then the cost. Every clause carries actionable information for an agent deciding whether to call and what to expect.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of explaining the return value and does so precisely (a download link, retained about an hour). With a single fully documented parameter, disclosed costs, and an annotation-covered safety profile, nothing material is missing for correct invocation.

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 the schema already explains the URL, name, and content_base64 variants and the 20 MB inline limit. The description adds only the per-file credit accounting, which hints that multiple files are accepted, but it adds no new meaning about the parameter's shape or constraints. Baseline 3 is appropriate.

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?

States a specific verb and resource pair ('Turn your PDFs into editable Word documents') with an unambiguous conversion direction that separates it from word_to_pdf and the pdf_to_excel/pdf_to_jpg siblings. The fidelity clause ('same fonts, margins, tables, columns and images') further pins down what kind of conversion this is.

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

Usage Guidelines3/5

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

Usage is implied by the input format constraint (.pdf) and the conversion direction, so an agent can infer when to call it. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of when ocr_pdf or split_pdf should come first, and no statement about prerequisites such as needing a public URL.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources