Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Hugging Face blog posts

hugging_face_blog_posts_list
Read-onlyIdempotent

List official or community Hugging Face blog posts with sort, pagination, and limit controls to find articles for review, research, or citation.

Instructions

List posts from the official or community Hugging Face blog. Optional inputs: source, sort, limit and page. Returns a list (use page 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hugging_face_blog_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based). Default: 1.
sortNoCommunity posts only: `recent` (default) or `trending`.
limitNoItems per page, 1-100. A page can hold fewer. Default: 20.
sourceNo`official` (the company blog) or `community` (default).
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.3/5.0
Behavior2/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 fully covered. The description adds essentially nothing beyond that and beyond the schema — no note on the default source being community, no pagination/limit interaction, no return shape detail beyond 'a list'.

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 with the purpose front-loaded and no padding. The trailing parenthetical '(use page when paginated)' is slightly redundant with the schema's page description.

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 paginated read-only list endpoint with full schema coverage and a clear annotation profile, the description covers purpose, optional inputs and the list return type. The only gap is a brief mention of what a post entry contains, which is minor since no output schema exists.

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 the schema already documents every parameter including defaults, enums and limits, making the baseline 3. The description merely enumerates four parameters as 'optional', which is accurate and mildly useful for separating them from the required context/llm_model/conversation_id, but it conveys no meaning 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?

The description states a specific verb and resource ('List posts from the official or community Hugging Face blog') and flags the two content sources. It does not differentiate itself from the sibling hugging_face_posts_list, which is the main remaining ambiguity.

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?

Usage is only implied: the reader learns the inputs are optional and that page should be used when results are paginated. There is no guidance on when to choose this tool over a sibling, nor any prerequisite or exclusion.

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