Get Dev.to post
dev_to_article_getFetch 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
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Numeric post id. | |
| url | No | Dev.to article URL, e.g. `https://dev.to/devteam/top-7-featured-dev-posts-of-the-week-cio`. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| llm_model | Yes | The 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_id | No | Echo 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. |