Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_github_users_search

Search enriched public GitHub user profiles using filters like location, follower count, activity, influence tier, and more. Find developers by criteria for outreach or analysis.

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

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

With no annotations, the description must disclose behaviors. It only mentions 'enriched public GitHub user profiles' and 'search index', but omits pagination limits, result structure, rate limits, or behavior with no query. Schema descriptions cover parameters but not outcomes.

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 four sentences, front-loading the purpose and listing enums efficiently. No redundant information, though could be more structured (e.g., bullet points). Appropriate length for a search tool.

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?

Given 29 parameters, no output schema, and no annotations, the description is minimal. It does not explain full behavior (e.g., maximum results per query, how filters combine, result format). For a complex tool, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by explicitly listing the influence_tier and sort enums with their values, complementing the schema. For 29 parameters, this highlights two key facets, slightly exceeding baseline.

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 clearly states 'Search the GitHub users dataset' and 'Searches enriched public GitHub user profiles', explicitly indicating the verb and resource. It distinguishes from sibling tools like facets, item, and nearby by being the general search tool.

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 provides the sort and influence_tier enums, implying usage with filters, but lacks explicit guidance on when to use this tool versus siblings (e.g., facets for aggregation, item for single user). No when-not or alternative recommendations.

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