| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Maybe explain that, unlike other form control elements so far, this is an _opt-in_ (and _why_).
return !ToolParamTitleAttribute(control).empty();Maybe we should also allow these inputs if `toolparamdescription` is set?
}We should also add some tests which check the actual input schema?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Maybe explain that, unlike other form control elements so far, this is an _opt-in_ (and _why_).
Done
return !ToolParamTitleAttribute(control).empty();Maybe we should also allow these inputs if `toolparamdescription` is set?
Done
We should also add some tests which check the actual input schema?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[WebMCP] Add parameter schema for <input type=hidden>
Allows <input type=hidden> elements to be included in the WebMCP tool
form schema, provided they include either a toolparamtitle or
toolparamdescription.
Since hidden fields are not user-facing, this requirement ensures
developers explicitly define the field's purpose for the AI agent.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |