You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quantitative (response size) + qualitative (schema & agentic usefulness) analysis of 9 representative GitHub MCP tools, one per available toolset.
Key findings today:
Best for agents:search_repositories ⭐⭐⭐⭐⭐ — flat, ~200 tokens, every discovery signal, zero bloat.
Worst:get_me ⭐ — returns 403 Resource not accessible by integration; the GITHUB_TOKEN has no user scope, so identity lookups are unavailable in this auth context.
Two pagination/bloat regressions worth flagging:
list_workflowsignored per_page=1 and returned 30 entries (~1650 tokens, total_count=324). Each carries badge_url/node_id/api-url that agents rarely use.
list_issues honored perPage=1 but inlined the issue's full multi-KB body (a token-audit report) → ~1400 tokens for one issue. A label-parsing artifact also split a single audit,token-usage label into two tokens.
list_code_scanning_alerts still inlines the full rule.help CWE markdown per result (~560 tokens for ONE alert #635 js/insecure-temporary-file, high severity, open since 06-22).
Snapshot: 9 tools · 5,550 tokens total · avg usefulness 3.33/5. 30-day window holds 191 data points across 21 days; rating trend stable (3.40 → 3.33).
Recommendations (tool selection for agentic work)
High-value (4–5):search_repositories, list_pull_requests, list_discussions, get_label, get_file_contents — prefer these for discovery/triage.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
GitHub MCP Structural Analysis — 2026-06-24
Quantitative (response size) + qualitative (schema & agentic usefulness) analysis of 9 representative GitHub MCP tools, one per available toolset.
Key findings today:
search_repositories⭐⭐⭐⭐⭐ — flat, ~200 tokens, every discovery signal, zero bloat.get_me⭐ — returns403 Resource not accessible by integration; theGITHUB_TOKENhas no user scope, so identity lookups are unavailable in this auth context.list_workflowsignoredper_page=1and returned 30 entries (~1650 tokens,total_count=324). Each carriesbadge_url/node_id/api-urlthat agents rarely use.list_issueshonoredperPage=1but inlined the issue's full multi-KB body (a token-audit report) → ~1400 tokens for one issue. A label-parsing artifact also split a singleaudit,token-usagelabel into two tokens.list_code_scanning_alertsstill inlines the fullrule.helpCWE markdown per result (~560 tokens for ONE alert #635js/insecure-temporary-file, high severity, open since 06-22).Snapshot: 9 tools · 5,550 tokens total · avg usefulness 3.33/5. 30-day window holds 191 data points across 21 days; rating trend stable (3.40 → 3.33).
Recommendations (tool selection for agentic work)
search_repositories,list_pull_requests,list_discussions,get_label,get_file_contents— prefer these for discovery/triage.get_label(45t/r4),list_discussions(210t/r4),search_repositories(200t/r5).list_workflows(1650t, ignoresper_page),list_issues(1400t, body inlined).list_code_scanning_alerts(moverule.helpto on-demand lookup),get_me(auth-limited — derive identity elsewhere).Full Structural Analysis Report
Executive Summary
Usefulness Ratings for Agentic Work
Schema Analysis
Response Size Analysis (today, 1 tool per toolset)
Tool-by-Tool Analysis
30-Day Trend Summary
Visualizations
Response Size by Toolset
Usefulness Ratings
Daily Token Trend
Size vs Usefulness
References: §28098801795
Beta Was this translation helpful? Give feedback.
All reactions