Sentry

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

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')

Find organizations that the user has access to in Sentry.

Use this tool when you need to:

• View organizations in Sentry

• Find an organization's slug to aid other tool requests

• Search for specific organizations by name or slug

Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.

Find projects in Sentry.

Use this tool when you need to:

• View projects in a Sentry organization

• Find a project's slug to aid other tool requests

• Search for specific projects by name or slug

Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.

Find releases in Sentry.

Use this tool when you need to:

• Find recent releases in a Sentry organization

• Find the most recent version released of a specific project

• Determine when a release was deployed to an environment

find_releases(organizationSlug='my-organization')

Find releases matching '2ce6a27' in the 'my-organization' organization

find_releases(organizationSlug='my-organization', query='2ce6a27')

Find teams in an organization in Sentry.

Use this tool when you need to:

• View teams in a Sentry organization

• Find a team's slug and numeric ID to aid other tool requests

• Search for specific teams by name or slug

Returns up to 25 results. If you hit this limit, use the query parameter to narrow down results.

Download attachments from a Sentry event.

Use this tool when you need to:

• Download files attached to a specific event

• Access screenshots, log files, or other attachments uploaded with an error report

• Retrieve attachment metadata and download URLs

get_event_attachment(organizationSlug='my-organization', projectSlug='my-project', eventId='c49541c747cb4d8aa3efb70ca5aba243', attachmentId='12345')

List all attachments for an event

get_event_attachment(organizationSlug='my-organization', projectSlug='my-project', eventId='c49541c747cb4d8aa3efb70ca5aba243')

Get tag value distribution for a specific Sentry issue.

Use this tool when you need to:

• Understand how an issue is distributed across different tag values

• Get aggregate counts of unique tag values (e.g., 'how many unique URLs are affected')

• Analyze which browsers, environments, or URLs are most impacted by an issue

• View the tag distributions page data programmatically

Common tag keys:

• url: Request URLs affected by the issue

• browser: Browser types and versions

• browser.name: Browser names only

• os: Operating systems

• environment: Deployment environments (production, staging, etc.)

• release: Software releases

• device: Device types

• user: Affected users

Get browser distribution using issue URL

get_issue_tag_values(issueUrl='https://sentry.io/issues/PROJECT-123/', tagKey='browser')

Get environment distribution

get_issue_tag_values(organizationSlug='my-organization', issueId='PROJECT-123', tagKey='environment')

Retrieve raw profile chunk data to inspect individual function calls, threads, and stack traces.

USE THIS TOOL WHEN:

• User wants to inspect raw profiling samples for a specific profiler session

• User needs to see individual thread activity and stack traces

• User wants detailed frame-level data (function names, file locations, call counts)

RETURNS:

• Profile chunk metadata (platform, release, environment)

• Per-thread sample counts and names

• Top frames by occurrence with file locations

• User code vs library code breakdown

NOTE: This tool requires a profilerId which identifies a specific profiling session. Use get_profile for aggregated flamegraph analysis by transaction name.

Fetch a Sentry resource by URL or by type and ID.

Breadcrumbs from a Sentry URL

get_sentry_resource(url='https://sentry.io/issues/PROJECT-123/', resourceType='breadcrumbs')

By type and ID

get_sentry_resource(resourceType='issue', organizationSlug='my-org', resourceId='PROJECT-123')

Search for events AND perform counts/aggregations - the ONLY tool for statistics and counts.

Supports TWO query types:

1. AGGREGATIONS (counts, sums, averages): 'how many errors', 'count of issues', 'total tokens'

2. Individual events with timestamps: 'show me error logs from last hour'

USE THIS FOR ALL COUNTS/STATISTICS:

• 'how many errors today' → returns count

• 'count of database failures' → returns count

• 'total number of issues' → returns count

• 'average response time' → returns avg()

• 'sum of tokens used' → returns sum()

ALSO USE FOR INDIVIDUAL EVENTS:

• 'error logs from last hour' → returns event list

• 'database errors with timestamps' → returns event list

• 'trace spans for slow API calls' → returns span list

Dataset Selection (AI automatically chooses):

• errors: Exception/crash events

• logs: Log entries

• spans: Performance data, AI/LLM calls, token usage

DO NOT USE for grouped issue lists → use search_issues

Search and filter events within a specific issue using natural language queries.

Use this to filter events by time, environment, release, user, trace ID, or other tags. The tool automatically constrains results to the specified issue.

For cross-issue searches use search_issues. For single issue or event details use get_sentry_resource.

Search for grouped issues/problems in Sentry - returns a LIST of issues, NOT counts or aggregations.

Uses AI to translate natural language queries into Sentry issue search syntax. Returns grouped issues with metadata like title, status, and user count.

USE THIS TOOL WHEN USERS WANT:

• A LIST of issues: 'show me issues', 'what problems do we have'

• Filtered issue lists: 'unresolved issues', 'critical bugs'

• Issues by impact: 'errors affecting more than 100 users'

• Issues by assignment: 'issues assigned to me'

• User feedback: 'show me user feedback', 'feedback from last week'

DO NOT USE FOR COUNTS/AGGREGATIONS:

• 'how many errors' → use search_events

• 'count of issues' → use search_events

• 'total number of errors today' → use search_events

• 'sum/average/statistics' → use search_events

ALSO DO NOT USE FOR:

• Individual error events with timestamps → use search_events

• Details about a specific issue ID or Sentry issue URL → use get_sentry_resource

REMEMBER: This tool returns a LIST of issues, not counts or statistics!

Identify the authenticated user in Sentry.

Use this tool when you need to:

• Get the user's name and email address.