Skip to main content
Glama

Devto

by io.github.pipeworx-io

Search Articles

search_articles
Read-onlyIdempotent

Search DEV.to articles by tag with pagination support. Returns title, author, tags, reactions, comments, reading time, and URL for each result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoTag to filter by (e.g., "typescript", "rust", "ai")
pageNoPage number for pagination (default 1)
limitNoNumber of articles per page (default 10, max 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number
articlesYesList of article summaries

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "page": 1,
+    "tag": "typescript"
+  },
+  {
+    "page": 2,
+    "tag": "rust"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "List of article summaries",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Article author information",
+            "properties": {
+              "name": {
+                "description": "Author full name",
+                "type": "string"
+              },
+              "username": {
+                "description": "Author username",
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "comments": {
+            "description": "Count of comments",
+            "type": "number"
+          },
+          "description": {
+            "description": "Article description or excerpt",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Article numeric ID",
+            "type": "number"
+          },
+          "published_at": {
+            "description": "Publication timestamp (ISO 8601 format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reactions": {
+            "description": "Count of public reactions",
+            "type": "number"
+          },
+          "reading_time_minutes": {
+            "description": "Estimated reading time in minutes",
+            "type": "number"
+          },
+          "tags": {
+            "description": "List of tags associated with article",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "description",
+          "url",
+          "published_at",
+          "tags",
+          "reading_time_minutes",
+          "reactions",
+          "comments",
+          "author"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    }
+  },
+  "required": [
+    "page",
+    "articles"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "limit": 10,
-    "page": 1,
-    "tag": "typescript"
-  },
-  {
-    "page": 2,
-    "tag": "rust"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "articles": {
-      "description": "List of article summaries",
-      "items": {
-        "properties": {
-          "author": {
-            "description": "Article author information",
-            "properties": {
-              "name": {
-                "description": "Author full name",
-                "type": "string"
-              },
-              "username": {
-                "description": "Author username",
-                "type": "string"
-              }
-            },
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "comments": {
-            "description": "Count of comments",
-            "type": "number"
-          },
-          "description": {
-            "description": "Article description or excerpt",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Article numeric ID",
-            "type": "number"
-          },
-          "published_at": {
-            "description": "Publication timestamp (ISO 8601 format)",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "reactions": {
-            "description": "Count of public reactions",
-            "type": "number"
-          },
-          "reading_time_minutes": {
-            "description": "Estimated reading time in minutes",
-            "type": "number"
-          },
-          "tags": {
-            "description": "List of tags associated with article",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "title": {
-            "description": "Article title",
-            "type": "string"
-          },
-          "url": {
-            "description": "Article URL",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "title",
-          "description",
-          "url",
-          "published_at",
-          "tags",
-          "reading_time_minutes",
-          "reactions",
-          "comments",
-          "author"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "page": {
-      "description": "Current page number",
-      "type": "number"
-    }
-  },
-  "required": [
-    "page",
-    "articles"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "List of article summaries",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Article author information",
+            "properties": {
+              "name": {
+                "description": "Author full name",
+                "type": "string"
+              },
+              "username": {
+                "description": "Author username",
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "comments": {
+            "description": "Count of comments",
+            "type": "number"
+          },
+          "description": {
+            "description": "Article description or excerpt",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Article numeric ID",
+            "type": "number"
+          },
+          "published_at": {
+            "description": "Publication timestamp (ISO 8601 format)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reactions": {
+            "description": "Count of public reactions",
+            "type": "number"
+          },
+          "reading_time_minutes": {
+            "description": "Estimated reading time in minutes",
+            "type": "number"
+          },
+          "tags": {
+            "description": "List of tags associated with article",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "description",
+          "url",
+          "published_at",
+          "tags",
+          "reading_time_minutes",
+          "reactions",
+          "comments",
+          "author"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    }
+  },
+  "required": [
+    "page",
+    "articles"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "page": 1,
+    "tag": "typescript"
+  },
+  {
+    "page": 2,
+    "tag": "rust"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds return field details, which is useful but not extra behavioral depth beyond annotations.

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?

Two sentences, no wasted words, front-loaded with key action and result details.

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

Completeness5/5

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

Given the output schema (implied by returned fields) and high-quality annotations, the description provides sufficient context for the agent to use the tool correctly.

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 covers 100% of parameters with descriptions. The description only restates the tag filter and pagination, adding no new meaning beyond the schema.

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 clearly states it searches DEV.to articles by tag with pagination, and lists the returned fields, distinguishing it from siblings like get_article or get_articles.

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 implies when to use (searching by tag) and mentions pagination, but does not explicitly state when not to use or name alternatives among siblings.

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

All Devto toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes with clear descriptions, but some overlap exists, e.g., ask_pipeworx vs ask_pipeworx_grounded, and several entity/company tools that could be confused. Overall, well-described and mostly disambiguated.

Naming Consistency5/5

Tool names follow consistent patterns: snake_case, with clear prefixes for each group (e.g., polymarket_*, pipeworx_*, get_article, etc.). Naming is predictable and systematic, making it easy to understand the tool's domain and action.

Tool Count2/5

33 tools is high for a server named 'Devto', where only a few tools actually relate to DEV.to. The majority are for Pipeworx data and Polymarket, which are unrelated. The tool count feels bloated and misaligned with the server's apparent primary purpose.

Completeness2/5

For the DEV.to domain, coverage is incomplete: lacks create/update/delete for articles and missing user profile management. The Pipeworx and Polymarket tools are extensive, but that doesn't compensate for the gaps in the core feature set implied by the server name.

Resources