Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dev.to post page details

dev_to_article_details_get
Read-onlyIdempotent

Fetch Dev.to post details, including series parts, comment IDs, and comment reactions, by post ID or article URL for content and discussion analysis.

Instructions

Get Dev.to post details: series parts, comment ids and comment reactions. Optional inputs: id and url.

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

Input Schema

NameRequiredDescriptionDefault
idNoNumeric post id.
urlNoDev.to article URL, e.g. `https://dev.to/devteam/top-7-featured-dev-posts-of-the-week-cio`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful information about what the response contains (series parts, comment ids, reactions), but says nothing about the `conversation_id` echo protocol or identifier-fallback behavior, which are the real behavioral traps here.

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?

Two short sentences with the resource and payload front-loaded, no filler. The second sentence largely duplicates what the schema already marks as optional, so it earns only partial keep, but the definition is tight overall.

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

Completeness3/5

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

With no output schema, the description partially compensates by listing returned fields, but it omits the rest of the payload (post body/metadata) and the conversational `conversation_id` handshake required by the schema. For a read-only detail getter it is adequate but leaves gaps an agent may hit on first invocation.

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 the schema already explains `id`, `url`, `context`, `llm_model` and `conversation_id` in detail. The description only restates that `id` and `url` are optional and adds no semantics such as precedence when both are given or the URL format accepted. Baseline 3 applies since the schema does the work.

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 gives a specific verb and resource ("Get Dev.to post details") and enumerates the distinctive payload — series parts, comment ids, comment reactions — which hints at how it differs from the plain article fetcher. It stops short of naming a sibling like dev_to_article_get or dev_to_article_comments_list, so the differentiation is inferred rather than stated.

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?

Usage is only implied: the mention of optional `id` and `url` suggests it is looked up by post identity, but there is no explicit when-to-use versus dev_to_article_get or dev_to_article_comments_list, and no note that at least one identifier must be supplied. An agent must reason from the returned-field list to decide between this and its siblings.

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