Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List GitHub profile activity

github_profile_activity_list
Read-onlyIdempotent

List recent public GitHub activity for a profile one month per request to review contributions; use the cursor to page backward through a selected year.

Instructions

List recent public activity for a GitHub profile, one month per request. 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_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year to read activity for. Default: current calendar year.
cursorNoPagination cursor from a previous response (`data.page.nextCursor`). Pages backward one month at a time through the selected year.
handleYesRequired. GitHub username whose public activity timeline 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.4/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 covered. The description adds two genuinely useful traits not in annotations: the one-month-per-call granularity and the cursor-based backward paging behavior. It says nothing about rate limits, errors, or what fields the returned list entries contain.

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 action and scope, followed by the prerequisite and the return/pagination note. The only redundancy is 'Requires handle', which the schema already marks as required.

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 no output schema, the description carries the burden of describing return values but only says 'Returns a list', leaving the shape of activity entries unstated. Parameter and safety information are adequately covered by the schema and annotations, so the gap is limited to return-value detail rather than correctness.

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 year, cursor, and handle are already fully documented, including that cursor pages backward one month at a time. The description only restates that handle is required and hints at cursor use, adding no meaning beyond the schema; 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 recent public activity for a GitHub profile') and adds scope ('public', 'one month per request'), which is enough for an agent to distinguish it from profile-get or repository-list siblings. It stops short of naming which sibling to use when the user wants contributions, comments, or pull requests instead.

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 'one month per request' and 'use cursor when paginated' notes give operational context, but there is no explicit when-to-use / when-not-to-use guidance and no statement of how this differs from the contributions or pull-request siblings. Usage is implied by the purpose rather than instructed.

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