> For the complete documentation index, see [llms.txt](https://fbl.fireblink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fbl.fireblink.com/flows/metadata.md).

# Metadata Fields

Metadata fields are used to provide additional information for FBL to change the action execution behavior.

Metadata fields are located on the same level as the action ID or alias and should always start with `$` character. E.g.:

```yaml
pipeline:
  $title: Assign 'value' to ctx.field
  ctx:
    '$.field':
      inline: 'value'
```

## $title

Title is used to make `--verbose` output more meaningful for the user. Instead of printing action ID or alias FBL will use the text inside the `$title` meta field.

## $parameters

Used to assign additional, provide initial or merge with existing parameters before running the action.

```yaml
pipeline:
  # provide parameters.test value right to the action
  $parameters: 
    test: true
  ctx:
    '$.field':
      # reference parameters field provided inside the metadata
      inline: $ref:parameters.test
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fbl.fireblink.com/flows/metadata.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.