Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List GitHub profile followers

github_profile_followers_list
Read-onlyIdempotent

List followers for a GitHub profile by providing a username; use the returned cursor to paginate through additional pages.

Instructions

List followers for a GitHub profile. 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_followers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response (numeric page index as a string).
handleYesRequired. GitHub username whose followers should be listed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds two useful facts beyond that: the operation is scoped to a required handle and pagination is cursor-based with the cursor coming from a prior response. It stops short of describing ordering, page size, or what a follower record contains.

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, front-loaded with the core operation and free of filler. The clause "Requires `handle`" is mild redundancy against the schema's required list, but it is cheap and aids scanning.

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?

This is a simple read-only list tool with complete schema documentation and full annotation coverage, so the burden on the description is low and what is there is sufficient to call it correctly. It is thin on the return shape (no output schema exists, and "Returns a list" does not say what each entry looks like) and silent on the shared context/conversation_id protocol, which an agent must read from the schema instead.

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 every parameter including the analytics-only context, llm_model, and conversation_id fields is already documented in the schema. The description restates handle as required and cursor as the pagination mechanism, adding no format or edge-case detail beyond what the schema supplies. Baseline 3 applies when the schema carries the semantics.

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 uses a specific verb and resource ("List followers for a GitHub profile"), which is unambiguous about what is returned. It does not, however, distinguish itself from the close sibling github_profile_following_list, leaving the direction of the relationship (followers vs. accounts followed) to be inferred from the name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, despite several plausible siblings in the catalog (following_list, followers_search, followers_verified). The only procedural hint is "use cursor when paginated," which is invocation mechanics rather than selection guidance.

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