Skip to main content
Glama

Search GitHub repositories, issues, code or users

github_search
Read-only

GitHub search with its own query syntax (e.g. 'sqlite language:rust stars:>100'). Repositories: name, owner, stars, forks, language, topics, licence, pushed date. Issues: title, state, labels, comments, URL. Code: path, repository and link. GitHub limits search to about 30 requests a minute; a busy minute is a 503, not charged. Limit max 30. Related tools on this server, for a different need: github_issues when you need to search a GitHub repository's issues or pull requests; github_releases when you need to list a GitHub repository's latest releases. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "github_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesGitHub search query, GitHub search syntax (1-256 characters)
typeNorepositories (default), issues, code or users
limitNoResults, 1-30 (default 10)

Output Schema

NameRequiredDescriptionDefault
typeNo
countNo
queryNo
sourceNo
resultsNo
checkedAtNo
totalCountNo
incompleteResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses rate limits, 503 behavior, success-based pricing, x402 payment networks, and that failed calls are not charged. Those are operationally important behaviors an agent would not know from readOnlyHint/openWorldHint alone.

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 definition is front-loaded and information-dense, with purpose and syntax before rate limits and pricing. Minor redundancy appears in the result-field lists despite an output schema, and 'Limit max 30' partly duplicates the schema.

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?

For a paid, rate-limited search tool with an output schema and safety annotations, the description covers the essential context: scope, syntax, rate limits, billing, and alternatives. Missing user-result field details are not a material gap because the output schema exists.

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 already 100%, so the baseline is 3. The description adds real value with a query-syntax example and a mapping of search categories to result fields, though it does not add much beyond the schema for limit defaults or type values.

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 states a specific verb and resource: GitHub search across repositories, issues, code, and users. It includes a concrete query example and explicitly distinguishes itself from sibling tools such as github_issues and github_releases.

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

Usage Guidelines5/5

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

It gives clear routing guidance: use this for general GitHub search, use github_issues for repository issues or pull requests, and github_releases for latest releases. That is an explicit alternative and condition, not just implied usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources