> 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/mcp-server/tools-and-support/tools.md).

# Tools

Find AirOps MCP tools for workspace data, analytics, Brand Kits, Playbooks, Workflows, Grids, and Knowledge Bases.

Use the AirOps MCP server to access and manage your workspace from Claude, Cursor, and other AI assistants. Choose a tool reference below for parameters, return values, permissions, and examples.

## Plan access

Resource tools require a paid workspace. Paid-tier trials remain eligible. Free workspaces can connect, discover tools, and use `list_workspaces`, but requests for their data return a plan restriction. If you belong to both Free and paid workspaces, choose a paid workspace for resource queries and changes.

## Tool reference

| Reference                                                     | What you can do                                                                                      |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| [Workspace & Brand Kits](broken://pages/0cphGzP4nUUA2Q0MvGdC) | Find workspaces and Brand Kits, manage brand content and visual assets, and publish approved drafts. |
| [Prompts & Answers](broken://pages/jD5I4qnl6ddcB1fMg6uX)      | Read tracked prompts and AI answers, and configure prompt tracking for a Brand Kit.                  |
| [Citations & Ads](broken://pages/WitWoKz191RQGKHl3Phs)        | Inspect citations, domains, observed ads, and advertisers for tracked prompts.                       |
| [Playbooks & Workflows](broken://pages/WPfCjnywP8sTUyxUdlyy)  | Read and edit Playbooks and Artifacts, review feedback, and run Playbooks and Workflows.             |
| [Analytics & Reports](broken://pages/Hy7T9KSCOSQZ2nzbY8c8)    | Query page performance, agent traffic, AI visibility analytics, and reports.                         |
| [Grids](broken://pages/4gIj0ObbgHat4vnZYo9U)                  | Read and write Grid data, configure columns, and run rows.                                           |
| [Knowledge Bases](broken://pages/kjUKkS4tTSGP3v7MjATE)        | Create and search Knowledge Bases, ingest content, and check indexing status.                        |

## Query Options

All list tools support:

| Option         | Description                                                              |
| -------------- | ------------------------------------------------------------------------ |
| **Filters**    | Narrow by field values (EQUALS, CONTAINS, EQ, NEQ, GT, LT, GEQ, LEQ, IN) |
| **Includes**   | Request related data in one call                                         |
| **Fields**     | Select specific fields to return                                         |
| **Sort**       | Order by supported fields (prefix `-` for descending)                    |
| **Pagination** | Control results with `page` and `per_page` (max 100)                     |

***

## AI Providers

Available provider values for filtering:

* `chat_gpt`
* `gemini`
* `perplexity`
* `google_ai_mode`
* `google_ai_overview`
* `claude`
* `microsoft_copilot`
* `grok`
* `muse_spark`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/mcp-server/tools-and-support/tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.