Skip to main content
Glama

JustFill PDF Form Automation

by io.github.mrmaciej1
OverviewDiscussionsAdmin

List saved templates

list_templates
Read-only

List saved, reusable form templates on the authenticated JustFill account.

Ordering & limit behavior: returns up to `limit` (default `50`) saved
calibration templates for the authenticated account, ordered from most
recently updated to oldest, as `templates` (`name`, `document_id`, and
`fields` count). Does not require an open workspace.

When to use:
- Use `list_templates` to inspect which reusable document templates are
  already saved on the user's account (via `save_template` or the web editor).
- Do not confuse with `list_fields`, which lists the individual fillable form
  fields (`id`, `name`, `x`, `y`, `w`, `h`) of a currently open `workspace_id`.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of most recently updated templates to return for the authenticated account (default `50`).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of most recently updated templates to return for the authenticated account (default `50`)."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly=true, destructive=false, and openWorld=false, but the description adds authentication scope, ordering behavior, default limit, return fields, and workspace independence. That is substantive behavioral context beyond annotations.

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-loads the purpose, then tight sections for ordering/limit and when-to-use guidance. The list_fields contrast includes a bit of field detail, but it earns its place by preventing a likely sibling mix-up.

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?

This is a low-complexity read tool with an output schema, rich annotations, and a complete description covering scope, ordering, limit, authentication context, and sibling differentiation. 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%, and the only parameter, limit, is already fully documented with its default and meaning. The description repeats the default and adds ordering context but little parameter-level meaning beyond the schema, so the baseline 3 applies.

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: list saved, reusable form templates on the authenticated account. It explicitly contrasts with list_fields, so an agent can distinguish it from the sibling without opening the schema.

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?

Gives explicit when-to-use guidance and a clear do-not-confuse rule with list_fields. It also states that no open workspace is required, which is a useful selection constraint.

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

All JustFill PDF Form Automation toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources