Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

github_search_users

Search public GitHub user accounts by query, with sort, order, and pagination controls. Retrieve total counts and profile details to find and analyze GitHub users.

Instructions

Search public GitHub users. Searches public GitHub user accounts with the required GitHub search query q. Order with sort (followers, repositories or joined) and order, and page with page and per_page (max 100). The response has total_count and items with login, id, profile URL, account type and match score.

Input Schema

Name	Required	Description
`q`	Yes	GitHub user search query
`page`	No	Page number
`sort`	No	Sort field
`order`	No	Sort order
`per_page`	No	Results per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / order / enum
```
Added value: +[
+  "asc",
+  "desc"
+]
```
- addedInput schema / properties / sort / enum
```
Added value: +[
+  "followers",
+  "repositories",
+  "joined"
+]
```
Addedv1.2.0Jul 6, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a fair job: it discloses the response shape (total_count plus items with login, id, profile URL, account type, match score) and the per_page cap of 100. It omits widely-relevant operational facts for GitHub search such as authentication requirements and the strict search rate limit.

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

Conciseness5/5

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

Three tight sentences: purpose first, then ordering/paging controls, then return shape. No filler, no repetition, and the most decision-relevant information (what it searches) is front-loaded.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields, and all five parameters are accounted for. It is nearly complete for a search tool; only auth/rate-limit context (notable for GitHub's search endpoints) is absent.

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, and the description largely restates the enum values and the max-100 cap. It does pair sort with order as a combined ordering operation, which adds slight semantic value, but the baseline of 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

The description opens with a specific verb+resource ("Search public GitHub users") and immediately narrows scope to public user accounts, distinguishing it from sibling repository/org/user-lookup tools. An agent can tell this is a user-account search without opening the schema.

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?

Usage is implied by the sort options (e.g., sorting by followers suggests discovery of prominent accounts), but there is no explicit when-to-use or when-not-to-use guidance. Alternatives such as github_user, github_user_followers, or datasets_github_users_search are never referenced, so the agent must infer routing on its own.

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

Deploy Server

github_search_users

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools