Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dev.to post

dev_to_article_get
Read-onlyIdempotent

Fetch a Dev.to article's complete Markdown and HTML content by post ID or URL for reading, parsing, or republishing.

Instructions

Get a Dev.to post with its full Markdown and HTML body. 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_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.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered; the description usefully adds that the response includes rendered HTML and Markdown bodies. It stops short of describing failure behavior (neither or both of id/url supplied, missing post, rate limits), which is the remaining behavioral gap for an open-world read.

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, front-loaded with the operation and its output. The second sentence restates schema-visible facts, so it earns less of its place than the first, but there is no bloat or redundancy elsewhere.

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?

There is no output schema, so the description has to carry return-value context, and it does partially by naming the Markdown and HTML body fields. For a fetcher with two identification paths and no documented precedence or error behavior, an agent still has unresolved questions before calling it 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 coverage is 100%, so the schema already documents all five parameters including the id/url examples and the context/llm_model/conversation_id conventions. The description's single line ("Optional inputs: `id` and `url`") adds nothing beyond the schema and slightly understates the practical requirement for at least one identifier. 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?

States a specific verb and resource ("Get a Dev.to post") plus the payload it returns ("full Markdown and HTML body"), which goes beyond the name. It does not, however, differentiate itself from the close sibling dev_to_article_details_get, so an agent cannot tell the two apart from the description alone.

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

Usage Guidelines2/5

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

No when-to-use guidance, no conditions, and no named alternatives. It also never states the selection rule between `id` and `url` (which to prefer if both are known, or that at least one is effectively needed), leaving the agent to infer usage entirely from the schema.

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