Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get GitHub profile

github_profile_get
Read-onlyIdempotent

Fetch a GitHub user or organization profile by username to look up public account details for identity, reputation, or contact checks.

Instructions

Get a GitHub profile for a user or organization. Requires handle.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. GitHub username to look up, with or without a leading @.
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 and network profile is fully covered. The description's only added behavioral context is that the lookup resolves both user and organization handles. It says nothing about rate limits, authentication, missing-handle behavior, or whether a 404-style miss is returned as an error.

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 sentences, no filler, and the resource identification is front-loaded. The second sentence is largely redundant with the schema's required list, which keeps it from being maximally efficient, but it is far from bloated.

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 lookup with rich annotations and a fully described schema, the definition is minimally sufficient. There is no output schema, so an agent cannot learn what fields a profile contains or how a nonexistent handle is surfaced, and the description does not compensate for either gap.

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%, so the schema already documents `handle` (including the leading-@ tolerance and the 39-character limit) and the analytics/conversation plumbing fields. The description repeats the `handle` requirement without adding format or edge-case detail, so the baseline of 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 concrete verb and resource ('Get a GitHub profile') and adds scope that matters: it works for either a user or an organization. An agent can tell it apart from the list/get sub-resources among the siblings (contributions, followers, repositories) because those are named for narrower resources. It stops short of explicitly naming a sibling it is not, so it is not a 5.

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 when-to-use guidance, no prerequisites, and no exclusions or alternatives. 'Requires `handle`' is a restatement of a required field rather than usage guidance, and nothing routes the agent between this tool and the many sibling profile 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