Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face members

hugging_face_organizations_members_list
Read-onlyIdempotent

List members of a Hugging Face organization by name, with optional name filtering and cursor pagination to retrieve large member lists.

Instructions

List every member of a Hugging Face 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_organizations_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
limitNoMembers per page, 10-1000. Default: 100.
queryNoOnly members whose name contains this text.
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

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds that the result is a list and that pagination goes through a cursor, but says nothing about authorization needs for private orgs, ordering of members, or whether the `query` filter is server-side.

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 resource and scope front-loaded and no filler. The middle 'Requires `name`' sentence is near-redundant with the mandatory schema field, which is the only wasted line.

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, four annotations, and no output schema, the description covers purpose, prerequisite, return shape and pagination. Remaining gaps (member ordering, org-visibility behavior) are minor for a straightforward enumeration endpoint.

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 `name`, `limit`, `query`, `cursor` and the meta parameters is already documented. The description restates only that `name` is required and gestures at cursor reuse, adding no filtering or ordering semantics beyond the schema.

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: listing every member of a Hugging Face organization, with the required `name` anchor. It is distinguishable from generic followers/likes siblings by the 'organization members' framing, but it never explicitly contrasts itself with `hugging_face_accounts_followers_list` or `hugging_face_users_following_list`, which are the closest alternatives.

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 description gives a pagination hint ('use cursor when paginated') and states the required parameter, which implies the call pattern but not when to prefer it. There is no statement of when-not-to-use it or which sibling handles follower/following enumeration instead, so the agent must infer the boundary from the tool name alone.

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