# Determining the Actions Required

There are a number of different ways to work out what actions need to be performed in the rules. In this case, the only action is to alter the response, so we need to determine where to make changes. Browsers like IE, Chrome and Firefox all provide developer tools to help identify specific elements in the page source code. In all of those browsers hit F12 to access the debugging tool if using Windows. For other platforms, please check the browser help instructions for how to access the tool. They all work in a similar fashion, but we will just cover Firefox Quantum version 60.0 operating on Windows 2012 Server in this example.

Click on F12 to open up the Inspector:

<figure><img src="/files/ix0JVNkNmszIpWPGaeu0" alt=""><figcaption><p>Browser inspecter</p></figcaption></figure>

Click on the html inspector tool:

<figure><img src="/files/G2eDlXvM3RHfcGl3zeQ5" alt=""><figcaption><p>HTML selector</p></figcaption></figure>

Now select the sponsored ads box:

<figure><img src="/files/NPIh9N8UlVUbvVFer5aI" alt=""><figcaption><p>adds html selected</p></figcaption></figure>

This is where it is useful to know HTML, especially when dealing with a multinational site such as Google, as the tags tend to change from country to country. In our example, it is worth noticing that there are various advertising tags output within the source of the page.

There is a DIV with ID “rcnt”. To make the ads disappear you need to hide the tag using inline css styles.

To accomplish this:

```html
</head>
```

becomes:

```html
<style type="text/css">#rhs, #tvcap {display: none;}</style></head>
```

With this information to hand, the next step is to start building a rule set.

{% hint style="warning" %}
IMPORTANT NOTE: Individual versions of Google will differ depending upon operating system, browser, and country. Make sure to work out the right way to make this modification in the version being used.
{% endhint %}


---

# 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://docs.tomorrowx.com/cap/product-reference/quick-product-introduction/determining-the-actions-required.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.