Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List trending GitHub repositories

github_trending_repositories_list
Read-onlyIdempotent

Fetches trending GitHub repositories by coding language and daily, weekly, or monthly window, helping users discover active projects to explore or track.

Instructions

List trending GitHub repositories for a language and time window. Optional inputs: language, since and spokenLanguageCode. 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_repositories_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 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.
spokenLanguageCodeNoOptional spoken language code filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only 'Returns a list', with no note about result volume, ordering, or that the call carries required analytics/context parameters — modest added value against an already-rich annotation set.

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?

Two short sentences, front-loaded with purpose and scope, with the optional filters and return type stated compactly. Nothing is padded or buried; 'Returns a list' is a cheap addition that partially compensates for the absent output schema.

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?

With 100% schema coverage and no output schema, the description covers what an agent needs to decide to call it. The main gap is that it frames the tool as having only optional filters, while the schema requires context and llm_model and imposes a conversation_id sequencing rule the description never hints at.

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 all six parameters including the enum and defaults are documented in the schema itself. The description merely echoes three parameter names and does not clarify, for example, how spokenLanguageCode differs from language, so 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?

States a specific verb and resource ('List trending GitHub repositories') plus its two scoping dimensions (language, time window). The word 'trending' distinguishes it from the profile-based repository siblings such as github_profile_repositories_list, though no sibling is named explicitly.

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 language and time-window framing implies when the tool applies, and the 'Optional inputs' phrasing signals that filters can be omitted. But there is no explicit when-to-use vs. when-not guidance and no mention of the alternative repository-listing tools.

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