Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_search_repositories

Search public GitHub repositories by query and filters to identify market or competitor projects through Crawlora MCP, returning structured JSON for research.

Instructions

Search public GitHub repositories. Searches public GitHub repositories (market/competitive discovery). Unauthenticated search is rate limited to roughly 10 requests per minute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesGitHub repository search query
pageNoPage number
sortNoSort field
orderNoSort order
per_pageNoResults per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / order / enum
      Added value: +[
+  "asc",
+  "desc"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "stars",
+  "forks",
+  "help-wanted-issues",
+  "updated"
+]
  2. Addedv1.2.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully discloses the unauthenticated rate limit (~10 requests per minute) and the public-only scope, which are meaningful operational constraints beyond the basic operation.

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 description is short, but the second sentence partially repeats the first ('Searches public GitHub repositories'). The rate-limit and use-case info are valuable, but the redundancy prevents a higher score.

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 search tool with no output schema and no annotations, the description covers the core purpose, scope, and a key operational constraint (rate limit). It does not mention output format or pagination behavior, but the schema covers pagination parameters and the rate limit is a critical contextual detail.

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 the schema already documents all five parameters. The description adds no additional parameter semantics (e.g., query syntax, default sort/order), so the baseline of 3 applies.

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?

The description states a specific verb and resource: 'Search public GitHub repositories.' The added use-case hint 'market/competitive discovery' gives context. However, it does not explicitly distinguish itself from sibling tools like github_search_users or github_user_repos, though the resource is clear enough.

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?

The description implies a use case (market/competitive discovery) but provides no explicit guidance on when to use this tool versus alternatives such as github_search_users or github_user_repos. No exclusions or alternative routing are mentioned, so the agent must infer usage from context.

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