Sentry.io

Retrieves the full detail of a single Sentry error event — stack trace, breadcrumbs, tags, and context — by its unique event ID.

Lists all raw events for a Sentry issue or project, enabling the agent to analyse error patterns, frequency spikes, and affected user counts across a time window.

Permanently removes a Sentry issue and all its events from the project, used to clean up test-environment noise or data-ingestion errors.

Fetches full metadata for a specific Sentry issue — status, assignee, event count, first/last seen timestamps, and tags — by its issue ID.

Lists issues in a Sentry project filtered by status, assignee, query, or date range, giving the agent a full view of the active error backlog.

Modifies a Sentry issue's status, assignee, priority, or ignore conditions — letting the agent triage and route errors without human intervention in the Sentry UI.

Creates a new Sentry project within an organisation, setting the platform, name, and team ownership — used when onboarding a new service or microservice.

Permanently deletes a Sentry project and all its data, used when decommissioning a retired service or cleaning up test projects.

Retrieves configuration details for a specific Sentry project — team ownership, platform, DSN, and feature flags — by its project ID.

Lists all Sentry projects within an organisation, enabling the agent to inventory services, check coverage gaps, or build cross-project reports.

Modifies a Sentry project's name, slug, platform, team assignment, or feature settings — used when a service is renamed or reassigned.

Creates a new Sentry release record tied to a version string, project, and commit range — enabling error attribution to specific deploys and session tracking.

Removes a Sentry release record, used to clean up accidental or test releases that should not appear in the release health dashboard.

Fetches a specific Sentry release by its version string, returning commit metadata, deploy history, and associated projects.

Lists all releases for a Sentry project or organisation, enabling the agent to build release history reports, compare crash rates, or identify regressions across versions.

Modifies a Sentry release to add commits, update references, or attach additional project associations after the initial record is created.

Creates a new Sentry organisation, used when provisioning isolated monitoring environments for new business units or enterprise clients.

Retrieves configuration and membership details for a specific Sentry organisation using its unique slug identifier.

Lists all Sentry organisations accessible to the authenticated token, used for cross-org reporting and multi-tenant management workflows.

Modifies an organisation's settings, name, or security configuration — used for bulk policy enforcement or rebranding after organisational changes.

Creates a new team within a Sentry organisation and assigns it to projects, used when onboarding a new engineering team or squad.

Removes a team from a Sentry organisation, typically as part of decommissioning a dissolved squad or cleaning up after a reorganisation.

Retrieves a specific team's details — membership, project associations, and access level — using the team's unique slug.

Lists all teams within a Sentry organisation, enabling the agent to build ownership maps, audit membership, or report on project coverage.

Fires when a new error group is first detected in Sentry, capturing the project, environment, and initial stack trace.

Fires when an issue is assigned to a team member or team in Sentry, including reassignments.

Fires when an issue transitions to the resolved state, either manually or via auto-resolve after a clean release.

Fires when an issue is ignored or muted in Sentry, including ignore-until-threshold and ignore-until-date conditions.

Fires when any team member posts a comment on a Sentry issue, capturing the author, body, and parent issue context.

Fires when a new release version is created and deployed in Sentry, including commit metadata and deploy environment.

Fires when a Sentry metric or issue alert rule threshold is breached, delivering the alert name, conditions met, and affected project.

Fires when Sentry's performance monitoring detects a statistically significant slowdown in a transaction compared to its baseline.