Handle pagination and optimize token usage #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fetching one page on paginated endpoints Issue: APPAI-32
timothedelion
force-pushed
the
tdelion/APPAI-32/optimize-token-usage
branch
from
3ebdc63 to
bff145e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1
The paginate_all method was only checking for "results" key in API responses, but some GitGuardian API endpoints return data using a "data" key instead. This caused get_all=True to fail by returning empty lists.
Added support for both response formats:
This fixes MCP tool calls with get_all=True parameter for endpoints like list_repo_incidents, list_repo_occurrences, and remediate_secret_incidents.