JustFill PDF Form Automation

Remove a field

remove_field

Destructive

Permanently delete a single false-positive field from the active workspace by its field_id.

Permanence & unknown-id behavior: immediately removes `field_id` from
`workspace_id` and returns `{"removed": 1, "fields_remaining": <count>}` (or
`{"removed": 0, "fields_remaining": <count>, "unknown_field_ids": [field_id]}`
if `field_id` is not found). Deletion is permanent within the active
workspace — to restore a deleted field, re-add it with `add_field` or re-open
the document with `open_pdf`. Saved account templates are unaffected unless
`save_template` is called afterward.

When to use:
- Use `remove_field` to delete one specific false-positive field box (e.g. a
  stray box over printed text).
- Use `remove_fields` to delete 2 or more known `field_id`s in a single batch
  call.
- Use `prune_fields` for rule-based bulk filtering by `confidence_below`,
  `width_below`, `height_below`, `field_type`, or `page_index`.

Input Schema

Name	Required	Description	Default
`field_id`	Yes	ID of the field to permanently delete from the workspace (from `open_pdf` or `list_fields`, e.g. `'p0_f3'`).
`workspace_id`	Yes	Active workspace ID returned by `open_pdf` (`summary.workspace_id`).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / field_id / description

Added value: +"ID of the field to permanently delete from the workspace (from `open_pdf` or `list_fields`, e.g. `'p0_f3'`)."

addedInput schema / properties / workspace_id / description

Added value: +"Active workspace ID returned by `open_pdf` (`summary.workspace_id`)."

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond destructiveHint=true by disclosing exact return payloads for both the success and unknown-id cases, stating deletion is permanent within the active workspace, specifying recovery paths (add_field, open_pdf), and noting the scope boundary that saved templates are unaffected unless save_template is called.

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?

Front-loaded with the destructive action and its permanence before any conditional detail, and the bulleted alternative routing is easy to scan. The inline JSON return snippets are somewhat verbose given an output schema exists, which keeps it just under top marks.

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 two-parameter destructive tool with full annotation coverage and an output schema, nothing an agent needs is missing: scope, permanence, recovery, error behavior, and sibling routing are all present. Return-value detail is technically redundant with the output schema but does not detract.

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 value: it ties field_id to a single false-positive box, defines the unknown-id outcome, and clarifies that removal is scoped to workspace_id's active workspace. It stops short of syntax examples, which the schema already supplies ('p0_f3').

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 ('Permanently delete a single false-positive field') and bounds it by workspace and field_id. The singular scope is explicitly contrasted with the plural and rule-based siblings, so an agent can distinguish it from remove_fields and prune_fields immediately.

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?

Provides an explicit 'When to use' block: remove_field for one specific field, remove_fields for 2+ known ids in a batch, prune_fields for rule-based filtering by named criteria. Each alternative is named with the condition that selects it, leaving nothing to inference.

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 tools Inspect

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.