Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List trending GitHub developers

github_trending_developers_list
Read-onlyIdempotent

Discover trending GitHub developers by programming language and daily, weekly, or monthly window, so you can identify active contributors and track community momentum.

Instructions

List trending GitHub developers for a language and time window. Optional inputs: language and since. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoTrending time window. Default: `daily`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoOptional trending coding language filter.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. Beyond that the description only adds "Returns a list", with no mention of result size, ordering, pagination, or rate limits typical of an open-world trending feed. Useful but thin given annotations do most of the work.

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, front-loaded sentences with zero filler, plus a terse returns note. The returns sentence is low value since there is no output schema, but it does not bloat the definition.

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 simple read-only list tool this is close to sufficient, and all five parameters are documented in the schema. However the description never mentions the required context/llm_model fields or the conversation_id sequencing constraint, which are the most error-prone parts of calling this tool.

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 coverage is 100% and the schema already explains language, since (with default daily), and the analytics/conversation parameters in detail. The description only restates that language and since are optional, adding no format or behavioral nuance beyond the schema.

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 trending GitHub developers") plus two scope dimensions (language, time window), which cleanly separates it from the sibling github_trending_repositories_list. It stops short of explicitly naming that alternative, so differentiation is inferred from the resource noun rather than stated.

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?

It notes the inputs are optional and that results are scoped to a language and time window, implying casual discovery use. There is no explicit when-to-use vs when-not statement or reference to a sibling tool for related lookups.

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