PulseAugur
EN
LIVE 03:57:08

Developer finds GitHub API sort order mismatch in tool documentation

By PulseAugur Editorial · [1 sources] ·

A developer discovered a subtle bug in their tool's documentation where the promised GitHub API sorting options did not align with the actual API's capabilities. The tool's docstring claimed support for sorting by 'stars' and 'forks', but the GitHub REST API endpoint used only accepted 'created', 'updated', 'pushed', and 'full_name' for user repositories. This discrepancy led to the API silently ignoring the invalid sort parameters and defaulting to its own order, creating a misleading success state for the tool. The developer fixed this by implementing client-side sorting for 'stars' and 'forks' after fetching the data, ensuring the tool's behavior now matches its documentation. AI

IMPACT Highlights the importance of accurate documentation and API contract adherence for AI agent tools.

RANK_REASON Article details a bug fix in a specific developer tool related to API interaction and documentation.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Developer finds GitHub API sort order mismatch in tool documentation

How we ranked this

Signal score
0 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
Article details a bug fix in a specific developer tool related to API interaction and documentation.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, other
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
78 days old
Aged out of breaking-news scoring windows; ranking reflects the durable signal from the full source set.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Enjoy Kumawat ·

    My MCP Tool's Docstring Promised sort="stars". GitHub's API Was Never Going to Honor That Value.

    <p>Every tool in my <code>developer-presence</code> MCP server has a one-line docstring, because that's the only documentation an agent calling the tool ever sees — no README, no OpenAPI spec, just whatever string sits under the <code>@mcp.tool()</code> decorator. I've already fo…

RELATED ENTITIES

RELATED TOPICS