Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to posts

dev_to_articles_list
Read-onlyIdempotent

List Dev.to posts by feed, tag, user, series, or top period to find articles for research, curation, or monitoring.

Instructions

List Dev.to posts: the feed, a tag, a user, a series, or the top posts of a period. Optional inputs: sort, tag, username, top, state and 3 more. 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_articles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoPosts with this one tag, e.g. `javascript`. Can be combined with `top`.
topNoMost-reacted posts of the last N days. Can be combined with `tag`.
pageNoPage number (1-1000). Default: 1. Live feeds move as posts are published, so a later page can repeat rows from an earlier one; dedupe by `id`.
sortNo`popular` (default) ranks the feed by recent engagement; `latest` is strictly newest first. Only for the unfiltered feed.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
stateNo`fresh` is posts with no reactions yet; `rising` is posts gaining reactions quickly. Cannot be combined with other filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
seriesIdNoParts of this series, oldest first (the `seriesId` of a post). Cannot be combined with other filters.
usernameNoPosts by this user or organization, newest first. Cannot be combined with other filters.
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.4/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. The description adds only a light pagination cue ('use page when paginated'); it says nothing about rate limits, auth needs, feed volatility, or result ordering beyond what annotations and schema supply. Useful but thin on top of the structured fields.

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 capability statement front-loaded, which is the right structure. Minor waste in the 'and 3 more' phrasing, which enumerates names already visible in the schema and ends on a vague count instead of the constraints that actually matter.

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 an 11-parameter listing tool with no output schema, the description conveys the modes and hints at pagination, and the rich schema fills in the rest. It omits the single most consequential behavioral fact for correct invocation, that several filters are mutually exclusive and `sort` only applies to the unfiltered feed, leaving that discovery to the schema.

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 enum meanings and mutual-exclusion constraints, is already documented in the schema. The description merely recites parameter names ('sort', 'tag', 'username', 'top', 'state') without adding interpretation, which is the baseline case rather than added value.

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 (list Dev.to posts) and enumerates the five modes it covers: feed, tag, user, series, and top-of-period. That is enough to separate it from most siblings, but it does not name or distinguish itself from the closely overlapping `dev_to_articles_search` or `dev_to_feed_home_list`, which an agent would have to resolve on its own.

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 mode list implies usage contexts (tag browsing, per-user listing, top posts), but the description never states when to prefer this tool over the sibling search or feed tools, nor does it warn which modes are mutually exclusive. The combination rules live only in the schema, so an agent must open the schema to learn that `state`, `seriesId`, and `username` cannot be mixed with other filters.

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