OpenAI API / OpenAI API

GitHub MCP Server list_commits causes OpenAI 429 rate-limit via bloated context

Understand how MCP server tool outputs bloat context windows and trigger API rate limits; find workarounds to trim response fields before sending to LLM Includes evidence for OpenAI API troubleshooting demand.

Source-backed Last updated May 20, 2026 1 source Needs local verification

Category: OpenAI API
Error signature: openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 20, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for OpenAI API, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490 is a OpenAI API failure pattern reported for developers trying to understand how mcp server tool outputs bloat context windows and trigger api rate limits; find workarounds to trim response fields before sending to llm. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Source: https://github.com/github/github-mcp-server/issues/142 — When list_commits() returns 30 results, each at 5-6KB, total context exceeds 64K tokens and triggers TPM 429 errors on OpenAI. Tier-1 API user affected. Issue actively discussed, recently closed May 21 2026 after minimal response trimming was added. Strong commercial value: affects paid API users + MCP ecosystem. Category = OpenAI API (root cause is rate limit triggered by tool output size).

Common causes

Source: https://github.com/github/github-mcp-server/issues/142 — When list_commits() returns 30 results, each at 5-6KB, total context exceeds 64K tokens and triggers TPM 429 errors on OpenAI. Tier-1 API user affected. Issue actively discussed, recently closed May 21 2026 after minimal response trimming was added. Strong commercial value: affects paid API users + MCP ecosystem. Category = OpenAI API (root cause is rate limit triggered by tool output size).

Quick fixes

Confirm the exact error signature matches openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490.
Check the OpenAI API account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490 exactly before applying the quick fix.
Compare the failing environment with OpenAI API versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490 mean in OpenAI API?

openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490 indicates the workflow described by "GitHub MCP Server list_commits causes OpenAI 429 rate-limit via bloated context" failed in a OpenAI API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490?

Check whether this cause matches your environment: Source: https://github.com/github/github-mcp-server/issues/142 — When list_commits() returns 30 results, each at 5-6KB, total context exceeds 64K tokens and triggers TPM 429 errors on OpenAI. Tier-1 API user affected. Issue actively discussed, recently closed May 21 2026 after minimal response trimming was added. Strong commercial value: affects paid API users + MCP ecosystem. Category = OpenAI API (root cause is rate limit triggered by tool output size).

Is the openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490 guidance source-backed?

The "GitHub MCP Server list_commits causes OpenAI 429 rate-limit via bloated context" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490?

For "GitHub MCP Server list_commits causes OpenAI 429 rate-limit via bloated context", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging openai.RateLimitError: Error code: 429 - Request too large for gpt-4o in organization on tokens per min (TPM): Limit 30000, Requested 68490?

For "GitHub MCP Server list_commits causes OpenAI 429 rate-limit via bloated context", collect the failing OpenAI API command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.