Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to comments

dev_to_article_comments_list
Read-onlyIdempotent

Retrieve paginated comments and replies from a Dev.to article or podcast episode to review and follow community discussion.

Instructions

List the comments and replies on a Dev.to post or podcast episode. Optional inputs: articleId, podcastEpisodeId, page and limit. 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_article_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of top-level comments (1-1000). Replies come with their comment. Default: 1. A full page may be followed by an empty page when the list ends exactly at a page boundary.
limitNoTop-level comments per page (1-1000). Default: 30. Replies are not counted.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
articleIdNoNumeric post id.
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.
podcastEpisodeIdNoNumeric podcast episode id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds only that the call returns a list and that paging may be needed; it does not mention rate limits, ordering, or what happens at page boundaries (that detail lives in the schema instead).

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?

Three short sentences, front-loaded with the core action and the return shape. The middle sentence restating the optional parameter names is largely redundant with a fully documented schema, which is the only real waste.

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 read-only paginated list tool with full schema coverage and annotations, the description covers what the tool does, what it returns, and how to page. The one meaningful gap is the unresolved relationship between articleId and podcastEpisodeId, which the word 'Optional' obscures rather than clarifies.

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 page, limit, articleId, podcastEpisodeId, context, llm_model and conversation_id are all documented in the schema itself, including the replies-not-counted nuance. The description merely enumerates parameter names without adding format or constraint detail, so the baseline 3 applies.

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 opens with a specific verb and resource: 'List the comments and replies on a Dev.to post or podcast episode.' That clearly separates it from the singular retrieval sibling dev_to_comment_get and from the many non-comment list tools. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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?

There is one concrete usage hint -- 'use page when paginated' -- which tells the agent how to continue a result set. However, no guidance is given on choosing between articleId and podcastEpisodeId, and the description calls both 'Optional inputs' even though listing comments with neither seems meaningless, leaving the agent to infer the selection rule.

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