Popular Sentry tools
- Who am I — Return the authenticated Sentry user.
- Find organizations — Find Sentry organizations accessible to the authenticated user.
- Find projects — Find projects in a Sentry organization.
- Search issues — Search Sentry issues using Sentry issue-search syntax. Defaults to unresolved issues.
- Get issue details — Get strongly typed details for one Sentry issue.
- Get issue activity — Get activity and human comments for one Sentry issue.
- Search issue events — Search the error events grouped into one Sentry issue.
- Get event stacktrace — Retrieve a full issue event, including stacktrace entries when Sentry provides them.
- Update issue — Assign an issue or update its status. This mutates visible Sentry state.
- Add issue note — Add a human-visible comment to a Sentry issue activity feed.
- add team to project — Grant a team access to an existing Sentry project. Use this tool when you need to: - Add another team to a project - Grant a team access without changing project metadata - Check whether a team already has project access before adding it <examples> add_team_to_project(organizationSlug=‘my-organization’, projectSlug=‘my-project’, teamSlug=‘my-team’) </examples> <hints> - Team access changes are separate from project metadata updates. - If the team is already assigned, this tool returns the current team list without making another change. </hints>
- analyze issue with seer — Use Seer to analyze production errors and get detailed root cause analysis with specific code fixes. Use this tool when: - The user explicitly asks for root cause analysis, Seer analysis, or help fixing/debugging an issue - You are unable to accurately determine the root cause from the issue details alone Do NOT call this tool as an automatic follow-up to get_sentry_resource. What this tool provides: - Root cause analysis with code-level explanations - Specific file locations and line numbers where errors occur - Concrete code fixes you can apply - Step-by-step implementation guidance This tool automatically: 1. Checks if analysis already exists (instant results) 2. Starts new AI analysis if needed (~2-5 minutes) 3. Returns complete fix recommendations <examples> ### User: “Run Seer on this issue”
analyze_issue_with_seer(issueUrl='https://my-org.sentry.io/issues/PROJECT-1Z43')### User: “Analyze this issue and suggest a fix”analyze_issue_with_seer(organizationSlug='my-organization', issueId='ERROR-456')</examples> <hints> - Only use when the user explicitly requests analysis or you cannot determine the root cause from issue details alone - Seer Autofix does not support metric alert issues (issueCategory: metric); use get_issue_details and search_events instead - If the user provides an issueUrl, extract it and use that parameter alone - The analysis includes actual code snippets and fixes, not just error descriptions - Results are cached - subsequent calls return instantly </hints>