Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_github_users_search

Search the GitHub users dataset. Searches enriched public GitHub user profiles stored in a search index. influence_tier enum: nano, micro, mid, macro, mega.

Instructions

Search the GitHub users dataset. Searches enriched public GitHub user profiles stored in a search index. influence_tier enum: nano, micro, mid, macro, mega. Sort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over login, name, company, bio and location, max 256 characters
latNoLatitude for radius filtering or distance sort
lonNoLongitude for radius filtering or distance sort
cityNoExact geocoded city filter, max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc
loginNoExact login filter, max 128 characters
stateNoExact geocoded state filter, max 128 characters
domainNoInterest-domain tag filter (e.g. ml-ai, web, devops), max 128 characters
is_botNoBot filter (normally false; the crawl skips bots)
is_orgNoOrganization filter (normally false; the crawl indexes individuals)
companyNoExact normalized-company filter, max 128 characters
countryNoExact geocoded country filter, max 128 characters
has_blogNoFilter by public blog/website presence
hireableNoFilter by the GitHub available-for-hire flag
radius_mNoRadius in meters, 1 through 50000; requires lat and lon when supplied
has_emailNoFilter by public email presence
min_reposNoMinimum public repository count
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
reachableNoFilter by any public contact channel
active_90dNoFilter by activity within the last 90 days
has_twitterNoFilter by public Twitter/X handle presence
country_codeNoExact ISO country-code filter, max 128 characters
max_followersNoMaximum follower count
min_followersNoMinimum follower count
influence_tierNoFollower-tier enum: nano, micro, mid, macro, mega
min_rank_scoreNoMinimum composite rank score
max_account_age_yearsNoMaximum account age in years
min_account_age_yearsNoMinimum account age in years
is_suspected_automationNoSuspected automation (commit-farm/mass-repo bots); omitted these are hidden by default, pass true to isolate them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / influence_tier / enum
      Added value: +[
+  "nano",
+  "micro",
+  "mid",
+  "macro",
+  "mega"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "rank_score_desc",
+  "followers_desc",
+  "account_age_desc",
+  "account_age_asc",
+  "distance_asc"
+]
  2. Changed1 schema field changedv1.5.0
    • addedInput schema / properties / is_suspected_automation
      Added value: +{
+  "description": "Suspected automation (commit-farm/mass-repo bots); omitted these are hidden by default, pass true to isolate them",
+  "type": "boolean"
+}
  3. Addedv1.2.0

TDQS

B3.1/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 usefully discloses billing (1 credit per record, minimum 2, empty result costs 2, full 100-record page costs 100), which is real value beyond the schema. However it omits return shape, default sort/filter interplay, and any rate-limit or auth context, leaving significant gaps.

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 what the tool does, which is good, but the second and third sentences re-list enum values already encoded in the schema, which is wasted space. The billing note is the only genuinely additive sentence.

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

Completeness3/5

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

For a 30-parameter search tool with no output schema and no annotations, the description is thin: it covers billing and enums but says nothing about defaults, result contents, or how filters combine. The thorough schema offset by the absence of annotations and output schema leaves it only minimally adequate.

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 30 parameters, establishing the baseline of 3. The description merely repeats the influence_tier and sort enum values that are already present in the schema, adding no new semantic detail.

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 (Search) and resource (GitHub users dataset) and clarifies the underlying data is enriched public GitHub user profiles in a search index. It does not explicitly distinguish itself from siblings like datasets_github_users_nearby or datasets_github_users_facets, so it falls 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 when-to-use guidance, no alternatives named, and no conditions for choosing this search over nearby/facets variants or the github_search_users sibling. The enum listings hint at capabilities but do not tell the agent when this tool is the right call.

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