devto-mcp

devto_get_my_articles

Retrieve a paginated list of your DEV.to articles, filtering by published, drafts, or all statuses.

Instructions

List articles created by the authenticated user. Requires DEVTO_API_KEY.

Args: status: Filter by status: 'all', 'published', or 'unpublished' (drafts). Default 'all'. page: Pagination page (default 1). per_page: Articles per page (1-30, default 10).

Returns: List of the authenticated user's articles including draft status.

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

Input Schema

Name	Required	Default
`page`	No
`status`	No	all
`per_page`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the auth requirement, that it returns drafts, and that the status filter affects published/unpublished/drafts. It does not cover rate limits or errors, but for a simple read operation this is quite transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured, front-loading the core purpose and auth requirement before organizing parameters under 'Args' and return under 'Returns'. Every sentence adds useful information with no filler.

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 three-parameter authenticated listing tool with an output schema, the description covers auth, parameter semantics, and the list/draft behavior. It would be slightly stronger with explicit sibling guidance, but nothing critical is missing for the tool to be called correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully document parameters. It does: status has explicit allowed values ('all', 'published', 'unpublished'), page has a default, and per_page has a range (1-30) and default. This exceeds what the bare schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('List articles') and a specific resource ('created by the authenticated user'), which clearly differentiates it from siblings like devto_list_articles or devto_search_articles. The inclusion of 'Requires DEVTO_API_KEY' further identifies the tool's function as user-scoped.

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 context is clear: use this for the authenticated user's articles, not for general article listing. However, it does not explicitly name alternatives or state when not to use this tool, leaving the agent to infer the distinction from sibling names.

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

Deploy Server