> 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 catalog The following Tools are available in the Playbook editor. Many of them power AEO and SEO research, so this catalog is also a quick reference for what AirOps includes for AI search and traditional search work. ### AirOps * **AirOps MCP:** Access your AirOps data, including Insights data, Brand Kits, Knowledge Bases, and Grids. * This Tool is always on. * **AirOps SEO Research:** Keyword research, domain analysis, and backlink data. * **Page 360 Report:** Build a full diagnostic for one owned URL before you refresh, expand, or troubleshoot it. Page 360 brings together GSC, GA4, and AEO performance trends, SEO keywords, won and missed AI prompts, AI referrers, page metadata, freshness signals, backlinks, link health, CTAs, authority signals, and scraped page content so the Playbook can see what to preserve and what to improve. * **Page Versus Report:** Build a competitive brief for one owned URL against the pages winning in search and AI answers. Page Versus can anchor the analysis to a target keyword or prompt, then compare competitor pages, keyword and content gaps, search intent, topic coverage, headings, FAQs, page structure, metadata, backlinks, and optional live citation checks across ChatGPT, Gemini, Perplexity, and Google AI Mode. * **Web Page Scrape:** Scrape content from web pages. ### SEO Research * **DataForSEO:** SEO data and keyword research. * **Moz:** SEO and domain analysis. * **Google Search Console:** GSC data. ### Web Research * **Google Search:** Search and retrieve Google results. * **Parallel Web Systems:** Use the Parallel Search API, Parallel Extract API, and Parallel Task API to run web research, pull structured data from URLs, and process research inputs into structured outputs. * **Firecrawl:** Crawl and scrape web pages. * **Reddit:** For more details, [Talk to Sales](https://www.airops.com/book-a-call). ### Image and Video * **Image Generation:** Generate hosted images with GPT Image 2 or Nano Banana 2. Hosted image outputs are useful when a downstream step publishes to a CMS. ### Knowledge Management * **Slack:** Read channel history and send messages. * **Google Docs:** Read and edit Google Docs documents. ### B2B Enrichment * **Brandfetch:** Retrieve brand assets and information. * **Hunter.io:** Find and verify email addresses. For more details, [Talk to Sales](https://www.airops.com/book-a-call). ### Paid Ads * **OpenAI Ads:** Retrieve insights from your OpenAI Ads account. {% 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 %} ## MCP Connectors Beyond the built-in catalog, you can add any MCP Connector configured in your workspace. MCP Connectors let a Playbook read context from and take action in external systems like Slack, Notion, GitHub, Asana, and your CMS. 1. Add the Connector in your workspace MCP Connectors settings. 2. Open the Playbook editor. 3. Type `/` in a Section and select the connected MCP tool. Connected MCP tools appear in the Playbook editor's Tools list alongside the built-in catalog. See [MCP](/mcp/getting-started.md) for setup and connector details. {% hint style="info" %} Use the native **Slack** Tool when a Playbook needs to read channel history or send messages. You can still add Slack through an MCP Connector if your workspace uses a custom connector setup. {% 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= ``` 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.