Search Dev.to posts
dev_to_articles_searchSearch Dev.to posts by keyword to find relevant articles, returning a paginated result list you can filter by recency and dedupe by post id.
Instructions
Search Dev.to posts by keyword. Requires query. 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": {
"query": "<query>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "dev_to_articles_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| top | No | Only posts from the last N days. | |
| page | No | Page number (1-1000). Default: 1. Live feeds move as posts are published, so a later page can repeat rows from an earlier one; dedupe by `id`. | |
| limit | No | Rows per page (1-1000). Default: 30. A page is the same price at any size. | |
| query | Yes | Required. Search text. Matches post titles, tags and bodies. | |
| 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. |