GitHub MCP Server

list_gists

Retrieve GitHub gists for a specific user or your authenticated account to view, manage, or analyze code snippets and notes.

Instructions

List gists for a user or the authenticated user.

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": "list_gists"
  }
}

Input Schema

Name	Required	Description
`username`	No	GitHub username (omit for authenticated user's gists)
`per_page`	No	Results per page (max 100)
`page`	No	Page number

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('List gists') but does not disclose behavioral traits such as pagination behavior (implied by parameters but not described), rate limits, authentication requirements, or what the output includes (though an output schema exists). This leaves gaps for an agent to understand operational 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 a single, efficient sentence that front-loads the core purpose ('List gists for a user or the authenticated user') with zero wasted words. It is appropriately sized for a straightforward listing tool.

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

Completeness4/5

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

Given the tool's low complexity (a read operation with pagination), 100% schema coverage, and the presence of an output schema, the description is mostly complete. It covers the purpose and scope but could improve by adding behavioral context (e.g., pagination details or authentication notes) to fully guide an agent, though the output schema reduces the need to explain return values.

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?

The input schema has 100% description coverage, clearly documenting all three parameters (username, per_page, page) with defaults and meanings. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage.

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 verb ('List') and resource ('gists'), specifying it can list for 'a user or the authenticated user'. However, it does not explicitly differentiate from sibling tools like 'get_gist' (which retrieves a single gist) or 'update_gist' (which modifies gists), though the distinction is implied by the 'list' action.

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 implies usage by mentioning it can list gists for a user or the authenticated user, which provides some context. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'get_gist' for a specific gist) or any exclusions (e.g., not for filtering by content).

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

Deploy Server