Get Profile Details
get_profile_detailsInspect a single Sentry transaction or continuous profile by ID, profiler ID, or URL to view trace, release, runtime, sample, thread, and top-frame details.
Instructions
Inspect one Sentry profile by profile ID, profiler ID, or URL: transaction, trace, release, and runtime details, sample and thread structure, and top frames. Handles transaction and continuous profiles. For aggregated hot paths across a transaction, use get_profile.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_profile_details"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | Continuous profile window end, ISO 8601; only with profilerId. | |
| fresh | No | Bypass cached reads. | |
| start | No | Continuous profile window start, ISO 8601 such as 2024-01-01T00:00:00Z; only with profilerId. | |
| profileId | No | Transaction profile ID. Do not combine with profilerId. | |
| regionUrl | No | ||
| profileUrl | No | Sentry transaction or continuous profile URL; the organization, project, and profile IDs come from it. | |
| profilerId | No | Continuous profiler session ID; requires start and end. | |
| focusOnUserCode | No | Show only application frames in the hotspot table; false includes library frames. | |
| projectSlugOrId | No | Project slug or numeric ID; required without profileUrl. | |
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| profile | Yes | ||
| samples | Yes | Null for legacy profiles, which have no sample-format data. | |
| suggestedActions | Yes |