> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ilitylabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools

> The tools the Ility MCP server offers, and how to point them at a workspace.

Each tool calls the [Ility API](https://docs.ilitylabs.com/api/overview.md) on your behalf, so it sees the same workspaces and returns the same errors an API client would see.

| Tool | What it does |
| - | - |
| `list_workspaces` | Lists the workspaces you belong to, with each one's id, name, your role, and which one tools use by default. |
| `list_domains` | Lists the websites in a workspace, with their slug, URL, plan, and latest scan state. |
| `get_domain` | One website by slug: its name, URL, plan, scan settings, and the surface it belongs to in Ility. |
| `get_domain_summary` | One website's accessibility summary: open issue counts by severity and pages scanned. |
| `list_issues` | Lists issues, newest first. Filter by domain, scan, page, rule, severity, status, or [label](https://docs.ilitylabs.com/issues/labels.md), or search the issue text. Only open issues unless you ask for other statuses. |
| `list_labels` | Lists the workspace's issue labels, with each one's id, name, color, and how many issues carry it. |
| `get_issue` | One issue in full: rule, WCAG criteria, severity, status, and how many pages and instances it affects. |
| `get_issue_fix_prompt` | A ready-made prompt describing how to fix one issue, with the failing markup and guidance. Hand it to a coding assistant working in the site's code. |
| `list_scans` | Lists scans across a workspace, newest first. Filter by status or domain. |
| `find_page` | Finds a page by its URL and returns its id, when it was last scanned, and its open issue counts. |
| `get_scan` | One scan's status, progress, page counts, and timing. |
| `trigger_scan` | Starts a scan of a website. Choose all pages or only unscanned ones, and optionally a WCAG version and level. |
| `scan_page` | Scans one page, by its id from `find_page`. Optionally choose a WCAG version and level. |
| `recheck_issue` | Rescans every page where an issue is still open, to check a fix. Instances that are gone are resolved when the scans finish. |
| `get_issue_timeline` | One issue's history, oldest first: comments, status changes, assignments, labels, and rechecks. |
| `list_members` | Lists the workspace's members, with the user ids `assign_issue` takes. |
| `comment_on_issue` | Adds a comment to an issue. Markdown works. |
| `set_issue_status` | Changes an issue's status to open, resolved, won't fix, or false positive, with an optional note saying why. |
| `assign_issue` | Assigns an issue to a workspace member, or unassigns it. |
| `set_issue_labels` | Replaces an issue's labels with the ones you list. Labels left out are removed. |

`trigger_scan`, `scan_page`, and `recheck_issue` start scans. The three scan tools need a plan that includes API triggers. Without one, they return an error naming `api_triggers_not_entitled`.

`comment_on_issue`, `set_issue_status`, `assign_issue`, and `set_issue_labels` change an issue. Each change shows on the issue's timeline under your name, marked with the assistant or API key it came through. Every other tool only reads.

## Working in Ility inside Claude

In Claude and other apps that show interactive views, three more tools open an interactive Ility view next to the conversation, so you can look through and change things yourself rather than through the assistant:

| Tool | What it opens |
| - | - |
| `open_ility` | Your workspace's sites, with open issue counts by severity and when each was last scanned. |
| `open_domain` | One site: its open issues, filterable by severity, its recent scans, and **Start scan**. |
| `open_issue` | One issue: set its status with an optional note, **Re-check** it, post a comment, and read its activity. **Open in Ility** opens the issue in the app. **Fix with Claude** asks Claude, in the conversation, to start a fix. |

Ask, for example, "Open my Ility sites" or "Show me this issue in Ility." Claude shows a card with **Open**, which opens the view in a side pane where Claude offers one, or full screen. Everything you do there goes through the same tools and permissions as the assistant's own calls. When you start a scan, change an issue's status, or re-check an issue, the assistant is told, so it can pick up from there.

In apps that can't show interactive views, these tools return the same data as `list_domains`, `get_domain_summary`, and `get_issue`.

## Linking to an issue

`list_issues`, `get_issue`, `get_issue_fix_prompt`, `set_issue_status`, `assign_issue`, and `set_issue_labels` return an issue's `app_url`: the issue's page in Ility, such as `https://app.ilitylabs.com/surfaces/<surface id>/issues/<issue id>`. Ask the assistant to put that link in a pull request, commit message, or ticket, so reviewers can open the issue in one click. Anyone who follows the link signs in to Ility and needs access to the issue's workspace.

## Choosing a workspace

Every tool except `list_workspaces` takes an optional `workspace_id`.

* Without it, a tool works in the default workspace: the one you picked when you signed in, or the workspace an API key belongs to.
* If you belong to several workspaces, the assistant can call `list_workspaces` and pass another workspace's id to work there. You can ask, for example "List the critical issues in the Acme workspace."
* An API key only works in its own workspace. Naming another workspace returns an error rather than quietly using the key's workspace.

## Slugs and ids

Domain tools, `list_scans`, and `trigger_scan` name a site by its **slug**, such as `www-example-com`. `list_issues` filters by the domain's **id** instead. Both come from `list_domains`. `get_domain` also returns a site's id when you already have its slug. The assistant handles the lookup when you name the site.

For prompts that work well, see [Common workflows](https://docs.ilitylabs.com/mcp/workflows.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.