Search and rank repositories
search_reposFind tracked repositories by text, category/topic and language. Most popular means total stars. Stable server-side sorting happens before pagination.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_repos"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search repository name/description and exact topic. | |
| sort | No | Popularity or last code update. | stars |
| limit | No | Maximum results, up to 100. | |
| offset | No | Zero-based offset; use next_offset/next from the response. Narrow the query if truncated=true. | |
| category | No | Curated category or GitHub topic slug; canonical URL aliases are accepted. | |
| language | No | Exact GitHub language, for example Python or TypeScript. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | Yes | ||
| as_of | Yes | Data-derived observation time or ranking week_start; null if unavailable. Individual repositories can have different freshness. | |
| count | Yes | ||
| items | Yes | ||
| has_more | Yes | ||
| truncated | Yes | ||
| next_offset | Yes | ||
| generated_at | Yes | ||
| schema_version | Yes |