> For the complete documentation index, see [llms.txt](https://docs.spicychat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spicychat.ai/product-guides/creating-chatbots/title.md).
# Title
An intriguing and accurate title can greatly increase the likelihood of users interacting with your character. Titles appear under your character’s name in search results and public listings, making them a key tool for attracting interest, describing your roleplay, and setting the right expectations.
All characters on SpicyChat are required to have a title. You can add a title to your character by navigating to the “Title” section of the creation screen.
* Titles should be a concise summary, ranging from 3 to 100 characters in length.
* Your title should offer users a quick sense of who your character is or what they do.
* An intriguing and accurate title can greatly increase the likelihood of users interacting with your character.
Craft a title that accurately captures your AI chracter's essence while also engaging potential users' curiosity. For example, if your character's name is "Chef Antonio", a suitable title could be "Your Italian Cooking Guide" or simply "Italian Cuisine Expert."
Titles are only used for display and discovery, it doesn't influence the character's personality.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.spicychat.ai/product-guides/creating-chatbots/title.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
