Skip to main content
Glama
Sign In
devto-mcp

devto-mcp

by AhmadTariq1337
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get my articles

devto_get_my_articles

Retrieve your own Dev.to articles with pagination and state filters. Choose published, unpublished, or all to manage your content.

Instructions

List the authenticated account's own articles.

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

NameRequiredDescriptionDefault
pageNo
stateNoall
perPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, but it does not disclose any additional behavioral traits such as pagination, default state filtering, or authentication requirements. This is minimal and leaves significant gaps for an agent to infer.

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, focused sentence that is front-loaded and free of unnecessary words. It is appropriately concise, though it could arguably contain more detail without sacrificing conciseness.

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?

The tool has no output schema and three optional parameters, yet the description does not explain return values, pagination behavior, or how the state parameter affects results. Given the minimal description and lack of structured output metadata, the description is not complete enough for an agent to use the tool confidently.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of the page, state, or perPage parameters. The agent must rely entirely on the schema's property names and constraints, which is insufficient for clear parameter understanding.

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 uses the specific verb 'List' and clearly identifies the resource as 'the authenticated account's own articles.' This distinguishes it from sibling tools like devto_list_articles, which likely lists all articles, and devto_get_article, which fetches a single article.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use this tool: when you need the authenticated user's articles rather than public articles or a specific article. However, it does not explicitly mention alternatives or exclusions, so it stops short of full guidance.

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