Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List GitHub profile pull requests

github_profile_pullRequests_list
Read-onlyIdempotent

List pull requests authored by a GitHub user, optionally filtered by creation date, and paginate results with a cursor.

Instructions

List pull requests authored by a GitHub user. 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_pullRequests_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly return pull requests created on or after this date (YYYY-MM-DD).
untilNoOnly return pull requests created on or before this date (YYYY-MM-DD).
cursorNoPagination cursor from a previous response (`data.page.nextCursor`).
handleYesRequired. GitHub username whose public pull requests 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

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 covered. The description adds only the pagination-cursor behavior and the required-handle constraint; it says nothing about rate limits, ordering, or result size.

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 the action and scope, then the prerequisite and pagination note. No filler or redundancy.

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?

For a read-only list tool with full schema coverage and rich annotations, the description covers purpose, prerequisite and pagination adequately. The only minor gap is that it does not mention the since/until date filtering, though the schema documents those fully.

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 since/until, cursor, context and llm_model is already documented in the schema. The description restates the handle requirement and cursor usage but adds no format or semantics beyond that, making the baseline 3 correct.

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 pull requests') plus a clear scope ('authored by a GitHub user'), which separates it from siblings like repositories_list or activity_list. It stops short of naming an alternative tool explicitly, so it lands at 4 rather than 5.

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?

Gives a prerequisite ('Requires `handle`') and a pagination hint ('use cursor when paginated'), which is useful operational context. It never says when to prefer this over sibling list tools or when-not to use it, so guidance is implied rather than explicit.

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