Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hugging Face account

hugging_face_accounts_get
Read-onlyIdempotent

Fetch a Hugging Face user or organization profile with follower counts, organizations, and profile text to support social data retrieval.

Instructions

Get a Hugging Face user or organization with its counts, organizations and profile text. Requires name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoExtra blocks, comma-separated. `socials` adds the social handles.
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.5/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 profile is fully covered elsewhere. The description adds useful scope information by naming the returned fields, but says nothing about authentication needs, rate limits, or what the `include` block (`socials`) changes in the response.

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, front-loaded with the resource and scope, with payload contents second. The closing 'Requires `name`' is redundant given the schema's required list, a small waste in an otherwise tight definition.

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 no output schema, the description partially compensates by summarizing the return shape (counts, organizations, profile text), and the injected context/llm_model/conversation_id parameters are self-documented in the schema. What remains missing is differentiation from the profile_get sibling, which matters for a five-parameter lookup 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 description coverage is 100%, so all five parameters (including the required context, llm_model and conversation_id) are already documented in the schema. The description restates the `name` requirement, which duplicates the `required` array rather than adding meaning; 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?

The description uses a specific verb and resource ('Get a Hugging Face user or organization') and enumerates the payload components (counts, organizations, profile text), so the agent knows exactly what comes back. It does not distinguish this from the sibling hugging_face_accounts_profile_get, leaving ambiguity about which account tool to choose.

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 only guidance is a prerequisite note ('Requires `name`'), which implies a direct lookup-by-identifier pattern. There is no statement of when to prefer this over profile_get or the various list tools, and no exclusions or edge cases (e.g., nonexistent account behavior).

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