Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face buckets

hugging_face_accounts_buckets_list
Read-onlyIdempotent

List the public storage buckets of a Hugging Face account to inspect available bucket IDs and verify what storage an account exposes.

Instructions

List the public storage buckets of a Hugging Face account. Requires name. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. Hugging Face user or organization name, e.g. `clem`.
queryNoOnly buckets whose id contains this text.
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=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully carried by structured data. The description adds the useful qualifier that only public buckets are returned, but says nothing about pagination, result limits, or failure behavior for a nonexistent account. "Returns a list" is minimal beyond the annotations.

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, front-loaded sentences with no padding; scope and the required input come first. "Returns a list" is close to tautological for a list tool, which is the only mildly wasted clause.

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 simple read-only listing with a fully documented schema and complete safety annotations, almost everything an agent needs is present. The remaining gap is that with no output schema, "Returns a list" doesn't describe bucket fields or pagination, but this is a minor omission for a low-complexity 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% and each of the five parameters is documented inline (including the query substring filter, context, llm_model, conversation_id). The description only echoes that `name` is required, which the schema already marks as required; it adds no interpretation the schema lacks, 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 specific verb (List), resource (public storage buckets) and owner (a Hugging Face account), and the scope word "public" narrows it meaningfully. Buckets are a distinct resource among the siblings, so an agent can distinguish it from repos_list or datasets_search without further help, though the definition never names a sibling.

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?

Only usage fact given is "Requires `name`", which is already enforced by the schema. There is no statement of when to prefer this over another listing tool, no note that private buckets are excluded, and no prerequisite/auth context beyond the implied account scope. Usage is inferable from the verb+resource but never spelled out.

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