Skip to main content
Glama

github_trending_repositories

github.com/trending — repos ranked by starsGained (daily|weekly|monthly), not all-time stars (2 credits). Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "github_trending_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 25, max 100). Flat 2 credits per call.
sinceNoTrending window: daily (default), weekly, or monthly — matches github.com/trending?since=.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
languageNoOptional programming-language slug (e.g. python, typescript) → /trending/{language}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  4. Changed4 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / language / description
      Previous value: -"Optional programming-language slug, e.g. python."New value: +"Optional programming-language slug (e.g. python, typescript) → /trending/{language}."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 25, max 100. Flat 2 credits per call."New value: +"Max items to return (default 25, max 100). Flat 2 credits per call."
    • changedInput schema / properties / since / description
      Previous value: -"daily (default), weekly, or monthly."New value: +"Trending window: daily (default), weekly, or monthly — matches github.com/trending?since=."
  5. Changed5 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional programming-language slug, e.g. python.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Billed per result."New value: +"Max items to return. Default 25, max 100. Flat 2 credits per call."
    • removedInput schema / properties / q
      Removed value: -{
      -  "description": "GitHub repository search query. Default stars:>1000.",
      -  "type": "string"
      -}
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "daily (default), weekly, or monthly.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "q"
      -]
  6. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  7. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  8. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does well: it discloses flat 2-credit pricing, that empty results and failures are never charged, that cache hits are free, and the default-fresh behavior. It omits auth requirements, rate limits, and any sense of response volume or pagination, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and ranking rule effectively, but the price is stated twice in immediate succession — '(2 credits). Costs 2 credits.' — which is wasted space in a five-sentence description. Otherwise there is little padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter read tool with no output schema and no annotations, the description covers the essentials an agent needs: what is ranked, the time windows, the cost model, and when caching applies. The main remaining gap is the shape of returned rows, which is only hinted at via the fields and compact parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (cache, limit, since, fields, compact, language) are already fully documented in the schema, setting the baseline at 3. The description reinforces cache semantics and the ranking metric behind 'since', but adds no syntax or format detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and ranking rule: repos from github.com/trending ranked by starsGained over daily/weekly/monthly windows, explicitly 'not all-time stars'. That implicitly separates it from github_repositories, but it never names a sibling or states the alternative route for all-time-star lookups, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives practical guidance on the cache flag ('Pass cache=true for a free 24h cache hit (default always fresh)') and ties the since values to github.com/trending?since=. It never says when to choose this over github_repositories or github_trending_developers, and gives no exclusions, so usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.