PulseAugur
中
实时 04:25:06
English(EN) "list_repos(limit=1, sort=\"stars\") Still Downloads 100 Repos From GitHub"

GitHub API 排序行为与工具文档不符

一位开发者发现,其与 GitHub 交互的 `my-git-manager` 工具中的 `list_repos` 函数在某些排序选项上的行为与文档不符。具体来说,当请求按“stars”或“forks”排序的仓库时,即使指定了较小的限制,该函数仍默认从 GitHub API 获取 100 个仓库。这是因为 GitHub API 仅在服务器端按“created”、“updated”、“pushed”或“full_name”进行排序,而对于“stars”和“forks”则需要客户端排序。开发者通过代码示例展示了这种差异,并指出该函数返回了请求数量的仓库,但在后台进行了更大的 API 调用,而用户对此并不知情。 AI

排序理由 开发者发现个人工具与平台 API 交互时存在功能差异。

在 dev.to — MCP tag 阅读 →

AI 生成摘要 · Google Gemini · 来自 1 个来源。 我们如何撰写摘要 →

GitHub API 排序行为与工具文档不符

本文如何被排名

Signal score
6 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
开发者发现个人工具与平台 API 交互时存在功能差异。
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
Low
Off-topic or adjacent — cluster remains reachable but doesn't surface in AI-industry rankings.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

完整方法见我们的编辑标准。

报道来源 [1]

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

    "list_repos(limit=1, sort=\"stars\") 仍从 GitHub 下载 100 个仓库"

    <p>I run a small MCP server for my own GitHub and DEV.to presence (<code>my-git-manager</code>, a FastMCP server with eight tools). One of them, <code>list_repos</code>, has a docstring that reads: "List public repos. sort: updated|created|pushed|full_name|stars|forks. limit: 1-1…