Finding tools
list_pr_findings
Section titled “list_pr_findings”List the findings of the latest b8e ci run uploaded for one pull request of a project, the same
list the dashboard’s pull request page shows. It requires a signed-in person; a machine credential
is refused.
| Name | Type | Required | Notes |
|---|---|---|---|
project_id | string | yes | |
repository | string | yes | The pull request’s repository as owner/name, e.g. acme/storefront. |
pr_number | number | yes | The pull request’s number. |
first | number | no | Page size. Default 20, max 100. |
after | string | no | Cursor from a previous call’s pageInfo.endCursor. |
Returns: { totalCount, pageInfo, findings }. totalCount counts every finding of the run, not
just the page, and is 0 when no b8e ci run was uploaded for the pull request. Each finding
carries id, fingerprint, location (a source path and line, or a page url), rule,
criterion, element, evidence, description, recommendation, impact, change and
seenAt. change is new when the previous run on the pull request’s branch did not have that
fingerprint, and carried_over when it did. These findings are not tickets.
Returns an error block reading Project "<id>" not found when no project matches. Any
other refusal comes back as an error block carrying the Binclusive API’s message.
list_scan_run_findings
Section titled “list_scan_run_findings”List the findings one b8e scan or b8e ci run uploaded, the same list the dashboard’s scan run page shows.
Take the run id from a CliScan entry of
list_project_run_history. It requires a signed-in person;
a machine credential is refused.
| Name | Type | Required | Notes |
|---|---|---|---|
scan_run_id | string | yes | The scan run’s id: scan_…, or, for a run moved over from scan tickets, the audit id it kept. |
file | string | no | Only the findings in this source path or on this page URL. |
impact | enum | no | Only the findings of this impact. See the generated ticket tool reference for accepted impact values. |
first | number | no | Page size. Default 20, max 100. |
after | string | no | Cursor from a previous call’s pageInfo.endCursor. |
Returns: { totalCount, pageInfo, findings }. totalCount counts every finding that matches
file and impact, not just the page. Findings come file by file: source files first, then
pages, each file’s findings in the order the run uploaded them. Each finding carries id,
fingerprint, location (ScanFindingSourceLocation with path and line, or
ScanFindingPageLocation with url, named in __typename), rule, criterion, element,
evidence, description, recommendation, impact, change and seenAt. change is new
or carried_over against the previous run on the run’s branch.
These findings are stored as the run uploaded them. They are not tickets, and the same issue in two runs is two findings.
Returns an error block reading Scan run "<id>" not found in this project when the run does not
belong to that organization and project, and nothing else.
create_ticket
Section titled “create_ticket”File an accessibility finding and its ticket into Binclusive. It arrives the same way one filed by
hand in the dashboard does, tagged origin: mcp so you can tell agent-filed findings from scanner
output later.
This is the one tool a machine (b8e_) credential can reach.
| Name | Type | Required | Notes |
|---|---|---|---|
project_id | string | yes | Project to file the finding under. |
organization_id | string | conditional | Required when signed in as a user; optional with a machine credential. See below. |
location | object | yes | A page or source location — see Vocabularies. |
criterion | string | no | WCAG success-criterion id, e.g. 1.4.3. Omit for a non-WCAG-mapped issue. Non-empty when present. |
element | string | yes | DOM selector / accessible-tree path locating the occurrence. Non-empty. |
evidence | string | yes | What was observed at the element. |
impact | enum | yes | See the generated ticket tool reference for accepted impact values. |
description | string | yes | Plain-language description of the issue. |
recommendation | string | yes | How to fix it — prose, not code. |
Which organization it files into
Section titled “Which organization it files into”| Signed in as | organization_id | What happens |
|---|---|---|
| A person | Required | You may belong to several organizations, so you have to say which. Omit it and the call is refused with create_ticket needs organization_id when signed in as a user — call list_organizations and pass the id of the organization to file into. |
A machine (b8e_) | Optional | The credential already names one organization. Pass an id anyway and it is checked against the credential; a mismatch is refused, not redirected. |
Choose an organization from get_viewer memberships or list_organizations and pass its id.
Returns: { findingId, ticket }, where the ticket carries id, url, element,
description, impact, wcagCriterion, status, priority, provenance, and createdAt.
Errors. With no credential present at all: create_ticket needs a credential to forward — none present. Sign in, or present a machine (b8e_) token. Otherwise the underlying error comes back in
full — a rejected impact value, a credential not allowed to file findings, or a project or
organization it cannot reach.