> 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.md).

# Tools

Tools are the actions a Playbook can take during a Session. A Playbook describes the work in natural language, and Tools are how it does that work: searching the web, pulling SEO and AEO data, scraping pages, generating images, and reaching into your stack through MCP Connectors.

Tools are one of the core building blocks of a Playbook, alongside Inputs, Sections, Artifacts, and Triggers. Without Tools, a Playbook can only reason over the context you pass in. With Tools, it can gather fresh data, take action in external systems, and ground its output in real research.

## How to add a Tool

Type `/` in any Section to open the slash menu. The slash menu surfaces Tools, Inputs, Artifacts, and other references you can insert directly into your instructions.

1. Place your cursor in the Section instruction where the Tool should be used.
2. Type `/` to open the slash menu.
3. Select the Tool you want.
4. The Tool appears inline as a gray pill with an icon.

Insert Tools from the slash menu instead of typing their names manually. Inserted Tools become easier to reuse, and the Playbook resolves them to the right action.

You can also review every Tool a Playbook uses from the header chip row above the first Section, which shows Tools, Inputs, Artifacts, and **Add Trigger**.

## Tool categories

The Playbook editor groups Tools by the work they help a Playbook complete. These categories cover the built-in Tool groups and MCP Connector setup.

* [**AirOps**](/actions/playbooks/tools/airops.md): Use AirOps workspace data, AEO and SEO reports, and page scraping.
* [**SEO Research**](/actions/playbooks/tools/seo-research.md): Pull keyword, domain, backlink, and search performance data.
* [**Web Research**](/actions/playbooks/tools/web-research.md): Search the web, scrape pages, crawl sites, and extract structured research.
* [**Image & Video**](/actions/playbooks/tools/image-and-video.md): Generate hosted images for downstream publishing.
* [**Knowledge Management**](/actions/playbooks/tools/knowledge-management.md): Work with Slack, Google Docs, Google Drive, Gmail, and Google Sheets.
* [**B2B Enrichment**](/actions/playbooks/tools/b2b-enrichment.md): Retrieve brand, contact, and review data.
* [**Paid Ads**](/actions/playbooks/tools/paid-ads.md): Pull OpenAI Ads performance insights.
* [**MCP Connectors**](/actions/playbooks/tools/mcp-connectors.md): Add workspace-configured connectors that extend the Playbook tool list.

{% hint style="info" %}
Tools for AEO and SEO research, such as the Page 360 Report, Page Versus Report, AirOps SEO Research, DataForSEO, Moz, and Google Search Console, work best when AirOps Insights is current. When a Playbook researches AI search visibility, point it at the prompts and LLM responses tracked in AirOps Insights rather than treating AI search as generic web research.
{% endhint %}

## Best practices

* Name the Tools a Section should use in that Section's instructions, and insert them from the slash menu so the Playbook resolves them reliably.
* Reference each Knowledge Base by name in Knowledge Base search steps instead of relying on auto-selection.
* For AEO and SEO research, keep AirOps Insights current so research Tools return data grounded in your tracked prompts and competitors.
* Use the **Image Generation** Tool when a downstream step needs hosted images, such as CMS publishing.
* When you convert a Workflow to a Playbook, confirm that Tools such as web scrape or Google Search carried through, and add any that did not.


---

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

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