# AI Rules

Glue **AI Rules let you personalize Glue AI's behavior,** ensuring that its responses and suggestions align with your unique communication style and preferences.

***

## 📘 What Are AI Rules?

AI Rules are user-defined instructions that guide Glue AI's interactions within the platform. Similar to Custom Instructions in other AI tools, these rules are currently set on a per-user basis. There are different types of rules you can set.

### Messaging Rules

Messaging Rules **guide how Glue AI interprets and responds to your direct requests** when you message Glue AI or @ mention Glue AI in a message. They allow you to specify preferences regarding tone, formatting, language, and more.

<details>

<summary><strong>Potential Use Cases for Messaging Rules</strong></summary>

* Giving Glue AI context on your role at your company.
* Ensuring responses maintain a professional tone.
* Requesting responses in a specific language or format.

</details>

### Suggestion Rules

Suggestion Rules customize how Glue AI proposes content within the Glue application, with options to set rules for **thread names, recipient suggestions, and group emojis.**

<details>

<summary><strong>Potential Use Cases for Suggestion Rules</strong></summary>

* **Thread naming** - Add prefixes, suffixes or naming conventions based on content
* **Thread recipients** - Encourage or discourage recipients depending on thread topic
* **Group emojis** - Have some fun and encourage use of certain emojis for team identification

</details>

### MCP Server Rules

You can also customize how Glue AI should interact with each MCP Server by configuring rules on a server by server basis. You can find more information about [configuring MCP Server rules here.](https://docs.glue.ai/mcp-servers#configure-rules-for-your-mcp-server-for-the-best-experience)

<details>

<summary>Potential Use Cases for MCP Server Rules</summary>

* **Store default values or IDs** (e.g., project or user IDs, board names) required when creating or updating items in external tools.
* **Define reusable templates** for common task types, messages, or request formats.
* **Enforce naming conventions** for tasks, documents, events, etc created via connected tools.

</details>

***

## How to set AI Rules for Glue AI

<details>

<summary>1) Open Glue preferences</summary>

* Click on your profile avatar in the upper-right corner of the Glue interface.
* Select **Preferences** from the dropdown menu.

</details>

<details>

<summary>2) <strong>Go to the Labs section and open AI Rules</strong></summary>

* In the Preferences menu, find and click the **Labs** tab.
* Under Labs, click the **AI Rules** feature. (If you don’t see it, check that the feature is enabled for your workspace or that you're on the latest version of Glue.)

</details>

<details>

<summary>3) <strong>Add rules to the Messaging and Suggestion Rules sections</strong></summary>

* You will see different sections for Messaging rules, and the Suggestion rules (thread naming, thread recipients, group emojis).
* Each has a text box where you can define your personal rules. You can enter multiple rules at a time in each text box.

</details>

<figure><img src="https://22865677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yStw8wuIeWBdGOh81bd%2Fuploads%2FeiyX6SDwQ3vk9fUwuNZQ%2FAI%20rules.png?alt=media&#x26;token=3dba4580-9c80-4f62-94a8-f61b12b837cc" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To [configure rules on an MCP Server](https://docs.glue.ai/mcp-servers#id-4-configure-rules-for-your-mcp-server-optional), go to the MCP Servers tab, click on the installed server and choose "configure rules."
{% endhint %}

***

## ✅ Tips for Writing Effective Rules

* **Be specific**: Clearly define your expectations and be as direct as possible.
* **Use full sentences**: Write rules like you’re giving instructions to a teammate.
* **Give context and examples where relevant**
* **Stay organized with one rule per line** for clarity (not required, but helpful to have line breaks for reviewing and editing your rules over time).
* **Test and revise**: Try out your rules, see how Glue AI responds, and refine them over time.

### Examples of AI Rules

<details>

<summary><strong>Messaging Rules Examples</strong></summary>

```
- Respond to all messages in a formal tone, using complete sentences.
- When discussing financial reports, assume the audience has a basic understanding of accounting principles.
- When summarizing meeting notes, use bullet points. E.g., '• Discussed Q3 targets • Reviewed marketing strategy.'
```

</details>

<details>

<summary><strong>Suggestion Rules Examples</strong></summary>

**Thread naming**

```
- If a thread context includes a link to a Linear issue or Figma file, prefix the thread name with "Project:" Don't add "Project:" if a user just types the the word "project" or "link".
- If the thread is describing a bug that a customer is experiencing or that the team has noticed via logs or reports, prefix the thread name with "🐛 Bug:"
```

**Thread recipients**

```
- If a thread is describing an API bug, suggest the API group.
- If the thread is describing a UI bug, suggest the Design group
```

**Group emojis**

```
- Use a different animal emoji for every department group, picking an animal emoji that fits with the team name.
```

</details>

***

## 🧠 Notes

* **Scope:** AI Rules are currently user-specific and cannot be applied at the workspace level.
* **AI Interpretation:** Glue AI may not always interpret complex or ambiguous instructions as intended.
* **Over-Specification:** Overly detailed rules might restrict Glue AI's ability to provide creative or flexible responses.
* **MCP Server Rules:** You can also define rules for MCP server behavior by configuring rules on the server once it’s set up.