# Output labels

Output (interface) labels should be clear and consistent so it is easy for users to understand their data and confidently map values between different modules. 

Consider the following when creating output labels:

* Use [sentence case capitalization](https://apastyle.apa.org/style-grammar-guidelines/capitalization/sentence-case). Capitalize only the first word and proper nouns.
* Use plain terms rather than API formats.
* Match terminology exactly. The output label must be identical to the corresponding mappable parameter.
* Follow the same order. The output labels and mappable parameters should be listed in the same order in both locations.

{% hint style="info" %}
Raw values (the actual keys returned by the API) shouldn’t be updated. They must be left as-is so they accurately reflect the external service's API documentation.
{% endhint %}

## Output label examples <a href="#capitalization" id="capitalization"></a>

| Correct       | Incorrect          |
| ------------- | ------------------ |
| Email address | Email Address      |
| User ID       | userID or user\_id |

{% tabs %}
{% tab title="Output labels" %}

<div align="left"><figure><img src="/files/8aCizTYIz9v5bcY3odtn" alt="" width="338"><figcaption></figcaption></figure></div>

This example from **Make AI Toolkit > Simple text prompt** follows the standard practices listed above.
{% endtab %}

{% tab title="Corresponding mappable parameter labels" %}

<div align="left"><figure><img src="/files/a6loTQ5wGCWuegvnX66i" alt="" width="290"><figcaption></figcaption></figure></div>

This example from **Make AI Toolkit > Simple text prompt** follows the standard practices listed above. The [mappable parameter labels](/custom-apps-documentation/best-practices/naming-conventions/input-parameters/parameter-labels.md) match the output labels for consistency and clarity.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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:

```
GET https://developers.make.com/custom-apps-documentation/best-practices/naming-conventions/output-labels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.