Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List GitHub profile repositories

github_profile_repositories_list
Read-onlyIdempotent

Lists public GitHub repositories for a specified user or organization, with sorting and cursor pagination to inspect profile projects.

Instructions

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

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "github_profile_repositories_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field for repositories.
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`.
cursorNoPagination cursor returned by a previous response.
handleYesRequired. GitHub username whose public repositories should be listed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
directionNoSort direction.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
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. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds two useful behaviors beyond that: `handle` is required, and pagination is cursor-based, so results must be paged. It says nothing about result ordering defaults, rate limiting, or whether private repos are included (only the schema's `handle` text says public).

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?

Two short sentences, front-loaded with purpose and the required parameter, with no filler. The trailing parenthetical "(use cursor when paginated)" is slightly compressed prose but still earns its place as the only pagination cue.

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?

With eight parameters, three required, and no output schema, the description does a reasonable job on the essential input and paging model. It does not explain the return shape (what fields a repository entry contains) or how the analytics-style params (`context`, `llm_model`, `conversation_id`) interact with listing, leaving those entirely to the schema.

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%, including enum explanations for `type`, `sort`, and `direction`, so the schema carries parameter meaning. The description adds only that `handle` is required and that `cursor` is a pagination token, which is a marginal restatement rather than new semantics; baseline 3 applies.

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 gives a specific verb and resource ("List repositories for a GitHub user or organization") and names the required key input (`handle`), so it is clearly distinguishable from github_repositories_get. It stops short of explicitly contrasting with that sibling or with github_profile_activity_list, so it is clear but not maximally differentiated.

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?

Usage is implied by the purpose: use it to enumerate a profile's repos. The only situational guidance is "use cursor when paginated," which is a pagination hint rather than a when-to-use/when-not rule, and no alternative tool is named for the single-repo case.

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

Deploy Server

Other Tools