Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Update hidden fields

update-hidden-fields-tool
Destructive

Replace a form's hidden fields — URL query parameters (e.g. utm_source, email) captured with each submission. Pass the COMPLETE list (fetch the current one with get-form-tool first) — it replaces the existing list. Max 50 fields; names up to 100 characters using letters, numbers, underscores, dashes, dots, and spaces. Pass an empty array to remove all hidden fields. Changes apply to the live form immediately — no publish needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_slug": "<form_slug>",
      "hidden_fields": "<hidden_fields>"
    },
    "name": "update-hidden-fields-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_slugYesThe form's slug.
hidden_fieldsYesThe complete list of hidden field names, e.g. ["utm_source", "email"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds the concrete consequences: the existing list is fully replaced, changes hit the live form immediately with no publish step, and there are hard limits (max 50 fields, 100-character names). That is substantive context beyond the structured hints.

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 action and the replace semantics, followed by the prerequisite fetch, constraints, and edge case. Four dense sentences with no filler and no repetition of the name or title.

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 mutation tool with no output schema, the description covers preconditions, replacement semantics, validation limits, the removal path, and live-effect timing — everything needed to invoke it correctly.

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 goes further by specifying allowed characters, name length, list size cap, and that the array must be complete rather than incremental. It adds real validation meaning the schema does not encode.

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 description names a specific verb and resource ('Replace a form's hidden fields') and immediately defines what a hidden field is ('URL query parameters captured with each submission'), which distinguishes it from siblings like update-variables-tool and update-translation-tool.

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 explicitly states the alternative workflow — fetch the current list with get-form-tool first — and explains the replace-not-merge semantics plus the empty-array case for removal. An agent knows exactly when and how to call this rather than guessing.

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

All Youform 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