Skip to main content
Glama

JustFill PDF Form Automation

Preview values in place

render_filled_preview

Preview how the filled page will look before fill_pdf. Costs nothing.

`values` maps field id -> text (checkboxes tick on "yes"/"x"/"true"). Text
placement, size and wrapping come from the same code as the export, with
the same flatten/fillable flags as fill_pdf. Not simulated: a watermark or
an account limit that stops fill_pdf.
In the JSON, `fit` lists values that were shrunk or cut and `warnings`
what to fix first. `preview_url` links to the same image; some clients
(e.g. ChatGPT) do not display tool images, so there the user sees the page
only through `preview_url`. Restricted data (payment cards, PHI,
government ids, or authentication secrets) is not accepted by this public
plugin.

When to use:
- Use `render_filled_preview` to verify text placement, alignment, and font
  sizing on each populated page at no cost before calling `fill_pdf` (required
  for every populated page on ML-detected layouts).
- Use `render_preview` to inspect empty field bounding boxes and `field_id`
  labels without values.
- Use `fill_pdf` once visual review is complete to generate the downloadable
  filled PDF.

Input Schema

NameRequiredDescriptionDefault
valuesYesMapping of `field_id` (from `open_pdf` or `list_fields`) to the string value to render. Checkboxes tick on `'yes'`, `'x'`, or `'true'`. Do not pass restricted data (payment cards, PHI, government IDs, or authentication secrets).
flattenNoIf `True` (default), bakes text statically into the page content. If `False`, preserves existing embedded AcroForm widgets as editable. Must match the `flatten` flag later passed to `fill_pdf`.
fillableNoIf `True`, synthesizes interactive AcroForm widgets on flat/scanned PDFs (takes precedence over `flatten`). Must match the `fillable` flag later passed to `fill_pdf`.
page_indexNo0-based page index (`0` to `page_count - 1`) of the document to render.
workspace_idYesActive workspace ID returned by `open_pdf` (`summary.workspace_id`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / fillable / description
      Added value: +"If `True`, synthesizes interactive AcroForm widgets on flat/scanned PDFs (takes precedence over `flatten`). Must match the `fillable` flag later passed to `fill_pdf`."
    • addedInput schema / properties / flatten / description
      Added value: +"If `True` (default), bakes text statically into the page content. If `False`, preserves existing embedded AcroForm widgets as editable. Must match the `flatten` flag later passed to `fill_pdf`."
    • addedInput schema / properties / page_index / description
      Added value: +"0-based page index (`0` to `page_count - 1`) of the document to render."
    • addedInput schema / properties / values / description
      Added value: +"Mapping of `field_id` (from `open_pdf` or `list_fields`) to the string value to render. Checkboxes tick on `'yes'`, `'x'`, or `'true'`. Do not pass restricted data (payment cards, PHI, government IDs, or authentication secrets)."
    • addedInput schema / properties / workspace_id / description
      Added value: +"Active workspace ID returned by `open_pdf` (`summary.workspace_id`)."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses zero cost, that rendering uses the same code path and flatten/fillable flags as the export, and crucially what is NOT simulated (watermarks, account limits). Also notes client-side image rendering limits (ChatGPT) and restricted-data rejection, which annotations do not cover.

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?

Front-loaded with the core purpose and cost in the first two lines, then structured bullets for usage. Every sentence carries operational information (flags, return keys, restricted data, client rendering) with no filler.

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?

No output schema exists, but the description fully documents the return payload (fit, warnings, preview_url) and the cost/safety model, so an agent has everything needed to call and interpret the result.

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, and the description adds real value: it restates the checkbox convention and stresses that flatten/fillable must match the later fill_pdf call, a cross-tool constraint not evident from the schema alone. It does not explain page_index or workspace_id beyond the schema, so it falls just short of 5.

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 first sentence states a specific verb and resource ('Preview how the filled page will look') and anchors it relative to a named sibling ('before fill_pdf'). An agent can immediately distinguish it from render_preview and fill_pdf.

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?

The 'When to use' block explicitly names the three relevant siblings and the condition selecting each: render_filled_preview for values/placement, render_preview for empty bounding boxes, fill_pdf for the final download. It also states the preview is required for populated pages on ML-detected layouts.

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.