Skip to main content
Glama
githunt-agent

GitHunt MCP

Search developers

search_developers
Read-only

Search a pool of GitHub developers by location, role, and skills. Get ranked candidates with fit scores, activity, and contact info for hiring.

Instructions

Search GitHunt's pre-indexed pool of GitHub developers by location, role, and skills. Returns candidates ranked by fit with scores, activity, and contact info. Fast (pool-served, no live crawl); page with offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoRole to rank candidates for. One of: fullstack, frontend, backend, mobile, devops, ai-engineer, ai-orchestrator, ml-engineer, data-scientist, data-engineer, security, cloud, blockchain, embedded, gamedev, ios-developer, android-developer, sre, platform-engineer, qa-engineer, solutions-architect, cto, vp-engineering, head-engineering, engineering-manager, tech-lead, product-manager, director-engineering.
offsetNoTop-ranked candidates to skip, for paging (0-200, default 0). Use with maxResults to fetch the next page. Each search scores at most ~200 candidates, so pages past that are empty.
skillsNoTechnologies or keywords to match, e.g. ['react', 'typescript']. Synonyms are handled (k8s -> kubernetes).
locationYesCity or country to search, freeform, e.g. 'Warsaw', 'San Francisco', 'Poland'. Common abbreviations and native names are normalized (SF, NYC, UK, Warszawa).
languagesNoProgramming languages to prefer, e.g. ['Python', 'Go'].
isHireableNoOnly candidates whose GitHub profile sets the 'hireable' flag.
maxResultsNoCandidates to return per call (1-100, default 25).
strictSkillsNoIf true, exclude candidates that match none of the given skills.
minExperienceYearsNoMinimum years since the GitHub account was created.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
resultsYes
totalCountNoTotal candidates matched before paging.
matchedCountYesCandidates returned in this page.
locationSuggestionsNoSimilar supported locations, present when the location matched nothing.
Behavior5/5

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

Annotations declare readOnlyHint=true. Description adds speed (no live crawl), pool-served nature, and paging details, all consistent.

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?

Two sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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

Completeness5/5

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

With full schema coverage, output schema, and paging details, description is complete for understanding tool behavior and expectations.

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% with detailed parameter descriptions. The tool description provides a high-level summary but does not add new meaning beyond schema.

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?

Clearly states it searches a pre-indexed pool of GitHub developers by location, role, skills. Distinct from siblings get_developer (single profile) and analyze_profile (analysis).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Mentions 'fast (pool-served, no live crawl)' and paging, giving context but not explicitly when not to use or alternatives. Implicitly distinct via tool name and siblings.

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/githunt-agent/githunt-mcp'

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