get_template_fields
Retrieve template fields with type, constraints, and required flag. Optionally return only required fields for minimum input.
Instructions
Return the fields belonging to a single template, with full field metadata.
Closes the most common pre-assign workflow gap: instead of fetching
list_template_definitions then list_field_definitions and
cross-referencing client-side, this returns the template's field
list directly with each field's type, constraints, and required
flag inlined. Use this BEFORE assign_template to construct the
fields argument.
Args:
template_name: Exact template name (case-sensitive on most
builds). Use list_template_definitions to discover
available names.
required_only: When True, return only fields where
is_required is true. Useful for "what's the minimum I
have to supply?" workflows.
Returns: {"template_name": <str>, "template_id": <int>, "field_count": <int>, "fields": [...]} where each field has
name, field_type, is_required, is_multi_value,
list_values, default_value, length, constraint.
On failure: returns {"mode": "error", "error": <slug>, ...}.
Slugs: invalid_template_name when the template name doesn't
exist in the repository (with the list of valid names in the
response); server_error for upstream issues.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| template_name | Yes | Exact template name (case-sensitive on most builds). Use list_template_definitions to discover available names. | |
| required_only | No | When True, return only fields where is_required is true — useful for 'what's the minimum I have to supply?' workflows. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||