Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_trending

List trending GitHub repositories and filter them by programming language or daily, weekly, and monthly windows to track popular projects.

Instructions

List trending GitHub repositories. Lists the repositories currently trending on GitHub. Filter by programming language (such as go or python) and choose the window with since (daily, weekly or monthly). Each repository has its owner, name, URL, description, language, stars, forks and stars gained today.

Input Schema

NameRequiredDescriptionDefault
sinceNoTime window
languageNoProgramming language filter (e.g. go, python)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / since / enum
      Added value: +[
+  "daily",
+  "weekly",
+  "monthly"
+]
  2. Addedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the returned fields (owner, name, URL, description, language, stars, forks, stars gained today), which adds real value given there is no output schema, but it says nothing about pagination, result limits, or ordering within the window.

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?

The opening two sentences are redundant ('List trending GitHub repositories. Lists the repositories currently trending on GitHub.'), wasting the most prominent position. The remaining content (filters, output fields) is useful and reasonably compact, but the leading duplication costs it.

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 two-parameter, zero-required, read-only list tool with no output schema, the description covers purpose, both parameters, and the shape of returned records. Only pagination/rate-limit context is missing, which is minor for this tool class.

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% and the `since` enum is fully enumerated in the schema, so the schema does the heavy lifting. The description restates the window options and gives language examples, but adds only marginal meaning beyond the structured fields.

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 verb+resource ('List trending GitHub repositories') that an agent can immediately act on. It does not, however, differentiate itself from close siblings like github_trending_developers (the developer counterpart) or github_search_repositories, so an agent must infer the distinction.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no named alternative. The description implies it is a 'browse what's hot now' tool but never tells the agent to prefer it over github_search_repositories for ad-hoc queries or over github_trending_developers for people.

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

Deploy Server

Other Tools