devto-mcp

Browse Dev.to articles

devto_list_articles

Browse public Dev.to articles by tag, author, or top period. Fetch paginated feed results to discover relevant posts.

Instructions

Browse the public Dev.to feed, optionally filtered by tag, author, or top-of-period.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devto_list_articles"
  }
}

Input Schema

Name	Required	Description
`tag`	No
`top`	No	Return top articles from the last N days instead of the latest feed.
`page`	No
`perPage`	No
`username`	No	Filter to articles by this author.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only reveals that the feed is 'public' (implying no auth), but says nothing about pagination behavior, response format, rate limits, or potential side effects. This is insufficient for a tool with no structured 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?

The description is a single, front-loaded sentence without fluff. It effectively communicates the core function, though additional details about filtering could be condensed without losing clarity.

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 with 5 parameters, no annotations, and no output schema, the description is too sparse. It lacks usage context, behavioral details, and does not address the pagination parameters or how it differs from sibling tools. This leaves the agent under-informed for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, with tag, page, and perPage lacking descriptions. The description mentions 'tag, author, or top-of-period' which adds some meaning to tag, username, and top, but it does not clarify page/perPage semantics or defaults. It partially compensates but leaves significant gaps.

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 'Browse the public Dev.to feed' clearly identifies the tool as listing public articles, with a specific verb and resource. It partially distinguishes from siblings like devto_get_article (single article) by implying a feed/list context, though it could be more explicit about it being a listing operation.

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?

The description provides no guidance on when to use this tool versus alternatives like devto_get_my_articles or devto_get_article. It implies usage for browsing the public feed but does not state exclusions or recommend sibling tools for other use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server