Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_github_users_search

Search enriched GitHub user profiles by location, skills, activity, follower count, and influence tier to find developers for recruitment or research.

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.

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
Behavior2/5

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

No annotations are present, so the description must fully convey behavioral traits. It only states it 'searches enriched public GitHub user profiles stored in a search index' but does not disclose read-only nature, rate limits, pagination behavior, or any side effects. The schema provides some details, but the description adds little transparency.

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

Conciseness4/5

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

The description is concise at two sentences (30 words). It is front-loaded with the verb 'Search' but lacks structure or bullet points. No unnecessary words, but could be more organized.

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?

With 30 parameters, no output schema, and no annotations, the description is minimally adequate. It does not explain return format, pagination constraints, or limitations. For a complex search tool, more context is needed for complete understanding.

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 coverage is 100% (all 30 parameters have descriptions). The description lists enums for influence_tier and sort, but these are already in the schema. It does not add new meaning or clarify parameter usage beyond the schema. Baseline 3 is appropriate.

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 tool searches the GitHub users dataset and searches enriched public GitHub user profiles. The verb 'Search' and resource 'GitHub users dataset' are specific. It does not explicitly distinguish from sibling search tools like datasets_github_users_facets, but the name and description make the purpose clear.

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 provided on when to use this tool versus alternatives. There is no mention of when not to use it or differentiation from other datasets_* tools. The description lacks any usage context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server