Skip to main content
Each tool calls the Ility API on your behalf, so it sees the same workspaces and returns the same errors an API client would see. 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: 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.