search_issue_events can't page past 100 events
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- api, backend-api-design
Research direction
Start with the tool schema in packages/mcp-core/src/tools/catalog/search-issue-events.ts:121-125 and the API client in packages/mcp-core/src/api-client/client.ts:3864-3901. Trace how the Sentry response’s Link header is handled and compare with tools that already accept a cursor, such as find_projects. Done when callers can request subsequent event pages and the returned events no longer stop at 100.
Written by the indexing model from the issue text.
Description
search_issue_events caps limit at 100 and has no cursor input, so an agent can't cover an issue with more events than that in the window. The Sentry endpoint it calls paginates; the MCP drops the cursor.
- Tool schema:
limitis.max(100)and there is nocursorparam (packages/mcp-core/src/tools/catalog/search-issue-events.ts:121-125). - API client sends only
per_page: limitand returnsdata, so theLinkheader cursor is lost (packages/mcp-core/src/api-client/client.ts:3864-3901). - Sentry
GET /organizations/{org}/issues/{issue}/events/usesself.paginate(..., paginator=GenericOffsetPaginator(...))(getsentry/sentrysrc/sentry/issues/endpoints/group_events.py:212-216@419d3dc). - Observed in a hosted MCP call (server 0.42.0, Claude):
limit=100, period=7dreturned exactly 100 events with no note that more exist, for an issue with ~850 events in that window.
Reported through MCP user feedback (MCP-SERVER-GN2). Related: other tools already take a cursor (find_projects, find_organizations, find_dashboards).
via Sentry.
--
- Dominant language
- TypeScript
- Stars
- 961
- Forks
- 179
- Avg merge
- 15h 33m
- Merged PRs (30d)
- 476
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/toolkit
-
MCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/toolkit#2276 · 1 comment ·
Maintainers usually reply within 1 day
-
CLI enhancement MCP
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
getsentry/toolkit#1908 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getsentry/toolkit#1471 · 1 comment ·
Maintainers usually reply within 1 day
-
get_sentry_resource gives no guidance for Explore > Errors list URLsPossibly taken @sentry-junior claimed this today. OpenMCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
getsentry/toolkit#2278 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
getsentry/toolkit#2275 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/toolkit
Similar issues
-
Add: BOM CineOpenapproved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug platform-android
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Termix-SSH/Mobile#146 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
devswha/herdr-web-ui#3875 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100