Skip to main content
Glama

Import a PDF into the editor

import_pdf

Returns a link (valid 24 hours) that opens an existing PDF in the ReflowPDF editor's import, which rebuilds it as an editable document. A PDF these tools printed, or one exported from the ReflowPDF editor with «Keep the PDF editable», opens from its own source at once; any other is rebuilt by AI, which needs a free account and uses its AI pages (the editor shows the cost first). A document you made with these tools needs no import: give the person its edit link. Give the PDF the person attached in the chat (pdf, as your client passes attached files), a public https URL of it, or its bytes in base64 (small files). A PDF you cannot pass on: the person opens the editor (https://app.reflowpdf.com) and imports it there.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "import_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfNoA PDF the person attached in the chat, as your client passes attached files to tools.
urlNoA public https address of the PDF.
nameNoThe document's name. Default: the file's.
pdf_base64NoThe PDF's bytes, base64 (up to 20 MB).

Output Schema

NameRequiredDescriptionDefault
urlYesThe link; it works until expiresAt.
notesYesWhat to tell the person about this link.
revisionNo
expiresAtYesWhen the link stops working (ISO 8601).
documentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pdf
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "A PDF the person attached in the chat, as your client passes attached files to tools.",
      +  "properties": {
      +    "download_url": {
      +      "description": "A temporary https address of the file.",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses that the returned link expires in 24 hours, that AI rebuilding requires a free account and spends AI pages, and that the editor shows the cost before committing. That is exactly the cost/auth/expiry context the agent needs before invoking a non-idempotent write.

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?

The purpose and link lifetime are front-loaded, and every sentence carries real information (instant-open vs AI rebuild, account requirement, input options, fallback). Some sentences are dense and nested, notably the «Keep the PDF editable» clause, which slows parsing slightly.

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?

For a mutation tool with zero required parameters, an output schema, and full schema coverage, the description supplies the missing decision layer: which input form to use, when not to use the tool, the account/cost prerequisite, and the manual fallback. Nothing an agent needs to call it correctly is absent apart from multi-parameter precedence.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds selection guidance beyond the schema: use the attached file object as the client passes it, a public https URL, or base64 only for small files. It does not state precedence when more than one of pdf/url/pdf_base64 is supplied, which is the remaining gap.

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 opening sentence states a specific verb (imports), the resource (an existing PDF), the outcome (an editable document in the ReflowPDF editor) and the return value (a link valid 24 hours). It is also clearly distinguished from siblings like open_in_editor and get_document by explaining that documents made with these tools need no import at all.

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

Usage Guidelines5/5

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

It gives explicit routing rules: PDFs printed by these tools or exported with «Keep the PDF editable» open instantly, anything else is AI-rebuilt and consumes AI pages requiring a free account, and documents created with these tools should be shared via their edit link instead. It also names the fallback when the PDF cannot be passed at all (the person imports it at app.reflowpdf.com).

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.