Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

search_users

Find GitHub users by search query with options to sort by followers, repositories, or join date, and filter results with pagination controls.

Instructions

Search for users on GitHub

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes
orderNo
pageNo
per_pageNo
sortNo

Implementation Reference

  • The core handler function implementing the search_users tool logic by querying the GitHub /search/users API endpoint.
    export async function searchUsers(params: z.infer<typeof SearchUsersSchema>) {
      return githubRequest(buildUrl("https://api.github.com/search/users", params));
    }
  • Zod schema definition for search_users tool input parameters (SearchUsersOptions), extending the base SearchOptions.
    export const SearchUsersOptions = SearchOptions.extend({
      sort: z.enum(["followers", "repositories", "joined"]).optional(),
    });
  • Alias for the SearchUsersOptions schema used throughout the codebase.
    export const SearchUsersSchema = SearchUsersOptions;
  • index.ts:148-152 (registration)
    Registration of the search_users tool in the MCP server's listTools response, defining name, description, and input schema.
    {
      name: "search_users",
      description: "Search for users on GitHub",
      inputSchema: zodToJsonSchema(search.SearchUsersSchema),
    },
  • index.ts:300-306 (registration)
    Dispatch handler in the MCP server's callTool request handler that parses arguments, calls the searchUsers function, and formats the response.
    case "search_users": {
      const args = search.SearchUsersSchema.parse(request.params.arguments);
      const results = await search.searchUsers(args);
      return {
        content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Search for users' implies a read-only operation, but it doesn't disclose important behavioral traits like pagination behavior (implied by page/per_page parameters), rate limits, authentication requirements, or what the response format looks like. The description is minimal and lacks behavioral context.

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?

The description is maximally concise with a single clear sentence that states the core purpose. There's no wasted language or unnecessary elaboration, making it efficiently front-loaded.

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?

For a search tool with 5 parameters (one required), no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't provide enough context about how to use the tool effectively, what parameters mean, or what to expect in return. The minimal description doesn't compensate for the missing structured information.

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

Parameters2/5

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

With 0% schema description coverage for 5 parameters, the description provides no parameter information beyond what's implied by the tool name. It doesn't explain what 'q' represents (search query), what the order/sort options mean, or how pagination works. The description fails to compensate for the complete lack of schema descriptions.

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 action ('Search for') and resource ('users on GitHub'), providing specific verb+resource pairing. However, it doesn't differentiate from sibling search tools like search_code, search_issues, and search_repositories, which all search different GitHub resources.

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 about when to use this tool versus alternatives. The description doesn't mention when this search is appropriate versus other user-related operations or how it differs from the other search tools on the server (search_code, search_issues, search_repositories).

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/PhialsBasement/mcp-github-server-plus'

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