Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_search_users

Find public GitHub developers by search query, with pagination, sorting, and ordering options to filter results for targeted discovery.

Instructions

Search public GitHub users. Searches public GitHub users (developer discovery). Unauthenticated search is rate limited to roughly 10 requests per minute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesGitHub user 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: +[
+  "followers",
+  "repositories",
+  "joined"
+]
  2. Addedv1.2.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It does disclose the unauthenticated rate limit of roughly 10 requests per minute and the public scope, which are useful. However, it does not mention response shape, pagination behavior, default ordering, or whether results follow GitHub search semantics.

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

Conciseness2/5

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

The first two sentences are almost redundant: 'Search public GitHub users' and 'Searches public GitHub users (developer discovery)' restate the same idea. Only the rate-limit sentence adds non-obvious value, so the structure is not tight enough for a higher score.

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

Completeness2/5

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

The tool has 5 parameters, no output schema, and no annotations, yet the description does not mention query syntax, result format, pagination defaults, or sort/order behavior. The rate-limit note helps, but an agent would still lack key information needed to invoke the tool confidently.

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 q, page, sort, order, and per_page. The description adds no parameter-level meaning beyond the schema, 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 clearly states the resource (public GitHub users) and the operation (search), and the parenthetical 'developer discovery' adds a use-case hint. It does not explicitly differentiate this from sibling tools like github_search_repositories or github_user, 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 Guidelines2/5

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

No guidance is given on when to choose this tool over alternatives such as github_user, github_user_repos, or github_search_repositories. The rate-limit note is an operational constraint, not a usage-selection guideline; exclusion conditions and alternative routing are absent.

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