What exists
The parser supports shared content, fields, images, and compatible URL buttons. Search/list views in selected commands have their own controls and authorization.What does not exist
The parser does not support template tags or blocks for multiple pages, previous/next buttons, or custom pagination state. Do not copy syntax from another implementation as if Headless executes it.Alternative
Split it into separate messages or use a native feature that already provides its own paginated view.Steps
1
Identify the output
Check whether you are configuring a message template or using a command with its own view.
2
Keep the template supported
Use only the syntax described in Embeds and Variables.
3
For large results
Prefer a native paginated response when a command offers one; do not add unrecognized tags.
The parser has no custom pagination command or tag. Page examples from another implementation are not Headless syntax.