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

# AirOps

AirOps Tools give Playbooks direct access to AirOps workspace data and built-in research reports. Use them when a Playbook needs Brand Kit context, Knowledge Base context, Insights data, page diagnostics, competitive page analysis, or scraped page content.

## Tools

### AirOps MCP

Access AirOps workspace data, including Insights data, Brand Kits, Knowledge Bases, and Grids. This Tool is enabled by default for new Playbooks.

Use **AirOps MCP** when a Playbook needs to:

* Pull Brand Kit context before drafting or reviewing content.
* Search a Knowledge Base for source material.
* Read Grid data or use Insights data tied to tracked prompts, pages, citations, and competitors.

### AirOps SEO Research

Retrieve keyword research, domain analysis, and backlink data through AirOps.

Use **AirOps SEO Research** for curated SEO lookups, such as keyword overview, related keywords, ranked keywords, site metrics, and linking domains.

### Page 360 Report

Build a diagnostic report for one owned URL before you refresh, expand, or troubleshoot it. Page 360 combines GSC, GA4, AEO performance trends, SEO keywords, AI prompt coverage, AI referrers, metadata, freshness signals, backlinks, link health, CTAs, authority signals, and scraped page content.

Use **Page 360 Report** when a Playbook needs a complete view of one owned page before recommending changes. Include the Brand Kit, page URL, and time range in the instructions.

### Page Versus Report

Compare one owned URL against pages winning in search and AI answers. Page Versus can anchor analysis to a target keyword or prompt, then compare competitor pages, keyword gaps, content gaps, search intent, topic coverage, headings, FAQs, page structure, metadata, backlinks, and optional live citation checks.

Use **Page Versus Report** when a Playbook needs competitive guidance. Include the owned page URL and either a target keyword, target prompt, or both. You can also tell the Playbook whether to focus on SEO, AEO, or both.

### Web Page Scrape

Scrape content from web pages for analysis, rewriting, enrichment, or source review.

Use **Web Page Scrape** when the Playbook needs page content as text, HTML, or markdown. For dynamic pages, tell the Playbook to render JavaScript or remove boilerplate if the main content is hard to extract.

## How to Configure

1. Open the Playbook editor.
2. Place your cursor in the Section instruction where the Tool should be used.
3. Type `/` and select the AirOps Tool from the menu.
4. Describe when the Playbook should use the Tool and what result it should produce.
5. For report Tools, include the page URL, Brand Kit, target keyword, or target prompt in the Section instructions.

## Parameters

| Tool                    | Required context                                                                        | Optional guidance                                                                                               |
| ----------------------- | --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **AirOps MCP**          | The AirOps resource to read from, such as a Brand Kit, Knowledge Base, Insight, or Grid | Explain which fields, files, prompts, or rows matter                                                            |
| **AirOps SEO Research** | Keyword, domain, URL, or competitor to research                                         | Add region, language, or comparison criteria                                                                    |
| **Page 360 Report**     | Owned page URL and Brand Kit                                                            | Add `7-days`, `30-days`, or `90-days` as the time range, plus any issues to inspect                             |
| **Page Versus Report**  | Owned page URL and Brand Kit                                                            | Add target keyword, target prompt, competitor limit, AI provider, citation check instructions, or SEO/AEO focus |
| **Web Page Scrape**     | URL to scrape                                                                           | Add output format, JavaScript rendering, proxy, headers, cleanup needs, or sections to extract                  |

## Examples

```markdown
Use **Page 360 Report** to analyze `target_url`. Preserve sections that drive search traffic, then identify content gaps and outdated claims.
```

```markdown
Use **AirOps MCP** to pull Brand Kit context before drafting. Apply the product line, audience, and writing rules that match this page.
```


---

# 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://docs.airops.com/actions/playbooks/tools/airops.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.
