Developers
Get access

stensul-run-quality-check

Runs the account's accessibility and quality checks on an email and returns the issues found.

readScope emails:read

Each issue has a readable message, a rule, and for element-level issues a locationText such as "the 2nd image in the 3rd module". An empty errors array means the email passed every active check.

Inputs

  • emailIdstring (24-char hex id)required

    Email to check.

Errors people hit

What you seeFix
401 Authentication expired or missing
The session's authorization expired.
Sign in again when the host prompts. On a 401 or 403, the server's instructions tell the model to re-check sign-in first.
403 Insufficient OAuth scope (403): The token lacks the required scope
The API connection doesn't have the scope this tool needs.
An admin adds the scope to the API connection. Then sign in again: adding a scope revokes existing tokens.
403 API error (403): Action is unauthorized.
The signed-in user's role lacks the permission, for example edit_campaign.
Grant the permission to the user's role in Admin > Users & Roles. It works for other users on the same connection.

All errors: Errors and troubleshooting.

{
  "emailId": "64f0c0ffee0000000000abcd"
}
Response

errors: a list of { message, rule, locationText? }. Empty when everything passes.

Described from the tool's definition. Captured responses from a Stensul-internal tenant will replace this.

Example values use invented brands and ids. Tool list captured 2026-09-28.

Esc