Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to feed

dev_to_feed_home_list
Read-onlyIdempotent

Fetches the public Dev.to home feed, including top comments under each post, with optional window and page parameters for pagination.

Instructions

List the public Dev.to home feed, with the top comments under each post. Optional inputs: window 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": "dev_to_feed_home_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-2000). Default: 1. Live feeds move as posts are published, so a later page can repeat rows from an earlier one; dedupe by `id`.
windowNoWhich feed: `home` (the front page, default), `latest`, or the most popular of the past `week`, `month`, `year` or `infinity` (all time).
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.1/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 structurally. The description adds one useful behavioral fact (top comments are embedded per post) but says nothing about result volume, ordering semantics, or the shifting-pagination caveat that only appears in the schema.

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 its distinctive return content. 'Returns a list' is mild padding given the verb is already 'List', but nothing is bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool whose schema mandates `context` and `llm_model` and whose `conversation_id` must be echoed from a prior response, the description omits all of that call protocol. Combined with the home-feed-only framing that understates the `window` enum, an agent could form a wrong picture of both what it may request and what it must supply.

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 `window`, `page`, and the meta-parameters in detail; a 3 is the appropriate baseline. The description merely names `window` and `page` as optional without adding meaning, and it never mentions the two required parameters (`context`, `llm_model`) at all.

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 verb+resource is concrete ('List the public Dev.to home feed') and the return contents ('top comments under each post') are stated. The only weakness is that it frames the tool as home-feed-only while the `window` enum exposes latest/week/month/year/infinity, so the stated scope is narrower than the tool's actual capability.

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?

There is no when-to-use vs when-not-to-use guidance, and no routing against plausible siblings such as dev_to_articles_list or dev_to_articles_search. The agent is left to infer that this tool is for the ranked/curated feed rather than filtered article listing.

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