Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Search Profiles

search_profiles
Read-only

Finds Sentry transaction and continuous profiles to return profile IDs, profiled transactions, counts, and aggregates; use results with get_profile for flamegraphs and hotspots.

Instructions

Search Sentry profiles: transaction and continuous profiles, to find profile IDs and profiled transactions. Returns individual events, counts, and aggregates; for grouped issue lists, use search_issues. Open a result with get_profile or get_profile_details for flamegraphs and hotspots.

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": "search_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field, - prefix for descending, such as -count() for aggregates. Omit unless you need a specific order.
freshNoBypass cached reads.
limitNoMaximum number of results to return.
queryNoWhat to find, in natural language or Sentry search syntax. Put environment, release, and other filters here.
fieldsNoColumns to return; omit unless you need exact columns. Include aggregates such as count() or avg() for statistics.
periodNoRelative time window, e.g. `30m`, `24h`, `7d`, `90d`.
regionUrlNo
projectSlugNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.
includeExplanationNoExplain how the query was translated or repaired.

Output Schema

NameRequiredDescriptionDefault
urlYesOpens these results in Sentry.
notesYes
queryYes
resultsYes
resultTypeYes
timeSeriesYes
explanationYes
executedSearchYes
presentationHintYes
suggestedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds return-shape information ('individual events, counts, and aggregates'), but that overlaps with the existing output schema, and it says nothing about pagination, result caps, or scope requirements beyond what parameters imply. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core purpose, then the disambiguation, then the next-step routing. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 mostly optional parameters, full annotation coverage, and a present output schema, the description supplies the essential framing: what is searched, what is returned at a coarse level, the sibling to avoid, and the drill-down tools. It stops short of noting practical constraints such as the 100-result limit or whether organization scoping is mandatory, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the schema already carries the burden for query, fields, sort, period, limit, and region/project/organization slugs. The description adds no syntax guidance, default-behavior notes, or examples for any parameter beyond the schema text, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Sentry profiles') and narrows the resource further to 'transaction and continuous profiles', with the concrete goal of finding profile IDs. It also explicitly distinguishes itself from the sibling search_issues for grouped issue lists, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusion/redirect ('for grouped issue lists, use search_issues') and a concrete follow-up path ('Open a result with get_profile or get_profile_details for flamegraphs and hotspots'). This tells the agent both when to pick this tool and what to do next with its results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.