JustFill PDF Form Automation

Remove many fields

remove_fields

Destructive

Permanently delete multiple fields by ID from the active workspace in a single batch mutation.

ID-list, partial-failure & persistence semantics: deduplicates `field_ids`,
deletes every matching field from `workspace_id`, and commits the updated
workspace state immediately. Returns `{"removed": <count>, "fields_remaining": <count>}`.
Any ID in `field_ids` that does not exist in the workspace is ignored during
deletion and reported in sorted `unknown_field_ids` while all valid IDs in
the batch are still removed (no error is raised for unknown IDs). Deletion is
irreversible within the active workspace — removed fields can only be
recovered via `add_field` or a fresh `open_pdf` call, and saved account
templates are not altered unless `save_template` is called afterward.

When to use:
- Use `remove_fields` when deleting an explicit list of 2 or more known
  false-positive `field_id`s at once.
- Use `remove_field` when deleting a single `field_id`.
- Use `prune_fields` for criteria-based bulk removal by `confidence_below`,
  `width_below`, `height_below`, `field_type`, or `page_index` instead of
  listing individual IDs.

Input Schema

Name	Required	Description	Default
`field_ids`	Yes	List of field IDs (from `open_pdf` or `list_fields`, e.g. `['p0_f2', 'p0_f5']`) to permanently remove from the workspace. Duplicate IDs are deduplicated; unknown IDs are ignored and returned in `unknown_field_ids`.
`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_ids / description

Added value: +"List of field IDs (from `open_pdf` or `list_fields`, e.g. `['p0_f2', 'p0_f5']`) to permanently remove from the workspace. Duplicate IDs are deduplicated; unknown IDs are ignored and returned in `unknown_field_ids`."

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?

Annotations only declare destructiveHint=true; the description goes well beyond that by disclosing irreversibility, the recovery paths (`add_field`, `open_pdf`), that saved templates are unaffected unless `save_template` is called, and the partial-failure rule that unknown IDs are silently skipped rather than erroring. It also states the returned counts and sorted `unknown_field_ids`, which is exactly the behavioral detail an agent needs before a destructive batch call.

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 scoped alternative routing, then grouped into a labeled semantics paragraph and a bulleted 'When to use' list. Slightly dense in the middle block, but every sentence carries operational information; 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?

For a destructive two-parameter batch tool with an output schema present, the definition covers safety, irreversibility, recovery, partial-failure behavior, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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; the description adds batch-level meaning the schema does not — that valid IDs are still committed when some IDs are unknown (no error raised for the batch), and where `workspace_id` comes from. Some overlap with the schema's dedup/unknown-ID notes, but the partial-failure framing is genuinely new.

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 multiple fields by ID'), plus scope ('from the active workspace in a single batch mutation'). It explicitly distinguishes itself from both `remove_field` (single) and `prune_fields` (criteria-based), so an agent can select it without opening any 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?

The 'When to use' block gives an explicit selection rule (2+ known false-positive IDs), names both alternatives by name, and describes the condition that routes to each (`remove_field` for one ID, `prune_fields` for confidence/size/type/page criteria). Nothing is left 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.