Skip to main content
Glama

List GitHub profile repositories

github_profile_repositories_list
Read-only

List repositories for a GitHub user or organization. Accepts a username. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field for repositories.
trimNoIgnored if this tool does not support it.
typeNoRepository type filter. `owner`: repos owned by the user. `all`: owned repos plus repos from organizations the user belongs to. `member`: only repos the user belongs to via organization membership (not owned by the user). Default: `owner`.
urlsNoAlias for `handle`. Prefer `handle`.
userNoAlias for `handle`. Prefer `handle`.
limitNoIgnored if this tool does not support it.
cursorNoPagination cursor returned by a previous response.
handleNoGitHub username whose public repositories should be listed.
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
pageSizeNoIgnored if this tool does not support it.
userNameNoAlias for `handle`. Prefer `handle`.
usernameNoAlias for `handle`. Prefer `handle`.
directionNoSort direction.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
profileUrlNoAlias for `handle`. Prefer `handle`.
linkedinUrlNoAlias for `handle`. Prefer `handle`.
max_resultsNoIgnored if this tool does not support it.
screen_nameNoAlias for `handle`. Prefer `handle`.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / linkedinUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / linkedinUrl / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / profileUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / profileUrl / type
      Removed value: -"string"
    • addedInput schema / properties / screen_name / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / screen_name / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / urls
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `handle`. Prefer `handle`."
      +}
    • addedInput schema / properties / user / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / user / type
      Removed value: -"string"
    • addedInput schema / properties / userName / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / userName / type
      Removed value: -"string"
    • addedInput schema / properties / username / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / username / type
      Removed value: -"string"
  2. Changed2 schema fields changed
    • addedInput schema / properties / linkedinUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / profileUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / screen_name
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / user
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / userName
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / username
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle"
      -]New value: +[
      +  "handle",
      +  "context",
      +  "llm_model"
      +]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / type / description
      Previous value: -"Repository type filter. Default: `owner`."New value: +"Repository type filter. `owner`: repos owned by the user. `all`: owned repos plus repos from organizations the user belongs to. `member`: only repos the user belongs to via organization membership (not owned by the user). Default: `owner`."
  7. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Repository type filter. Defaults to owner."New value: +"Repository type filter. Default: `owner`."
  8. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=true), lowering the bar. The description adds that the tool 'Returns a list (use cursor when paginated),' which is genuinely useful behavioral context, though the cursor parameter is already documented in the schema. No mention of error behavior, rate limits, or invalid-username handling, and no contradiction with annotations.

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?

Three short sentences with the core purpose front-loaded. The pagination instruction earns its place, and there is no filler or repetition of schema content.

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

Completeness3/5

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

For a read-only list tool with protective annotations and full schema coverage, the essentials are present: purpose, target, and pagination. Gaps remain: it does not differentiate itself from github_repositories_get or github_trending_repositories_list, and with 21 parameters and no output schema, a sentence describing what each repository entry contains would meaningfully improve completeness.

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 description coverage is 100%, so the baseline is 3 even without parameter info in the description. The description confirms the primary input ('Accepts a username'), matching the handle parameter, but adds nothing beyond the schema, which already documents aliases, defaults (type defaults to owner), and the meaning of each enum.

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?

States a specific verb ('List') and resource ('repositories') with a defined scope: 'GitHub user or organization.' This distinguishes it from siblings like github_profile_get, github_trending_repositories_list, and github_repositories_get by name and action, though it does not explicitly contrast them. The phrase 'Accepts a username' is slightly confusing given the claim that it also works for organizations.

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 when-to-use or when-not-to-use guidance, and no alternatives are named. An agent must infer the appropriate context from the tool name and the generic first sentence; there is no indication of how this differs from github_repositories_get or github_trending_repositories_list. The only operational hint is the pagination note ('use cursor when paginated').

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.