Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face activity

hugging_face_accounts_activity_list
Read-onlyIdempotent

List a Hugging Face user's or organization's recent public activity by name. Use the returned cursor to page through results when more activity exists.

Instructions

List the recent public activity of a Hugging Face user or organization. Requires name. 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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_accounts_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
limitNoItems per page, 1-100. A page can hold fewer. Default: 20.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep every other parameter the same.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without the description. The description does add that only *public* activity is returned and that pagination is cursor-based, which is useful beyond the annotations, but it omits rate limits, ordering, or what an activity item contains.

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 with the scope front-loaded and the pagination note last, so nothing buries the key point. Minor waste in 'Requires `name`', which duplicates the schema's required list.

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 list tool with full schema coverage and strong annotations, the definition is roughly sufficient, and it correctly notes the absence of an output schema by saying a list is returned. It leaves the pagination contract and item shape under-specified for an agent that needs to chain calls.

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?

With 100% schema description coverage, the schema already documents name, limit, cursor, and the meta-parameters, so baseline 3 applies. The description's mention of `name` being required and using the cursor merely restates schema content rather than adding hint or format detail.

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 (list) and resource (recent public activity) scoped to a Hugging Face user or organization, which distinguishes it from siblings like repos_list or followers_list by subject matter. It stops short of explicitly naming which sibling to use for other account data, so it lands just below 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?

Gives no when-to-use or when-not-to-use guidance and does not point at alternatives such as hugging_face_accounts_repos_list or hugging_face_accounts_followers_list. The only rule offered ('Requires `name`', 'use cursor when paginated') is procedural rather than comparative.

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