Get Dev.to trend
dev_to_trend_getFetches a trending Dev.to topic and its top posts so you can track what developers are discussing. Look up by trend id or slug and request paged article lists.
Instructions
Get a trending Dev.to topic with its top posts. Optional inputs: id, slug, include, page and limit.
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_trend_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Numeric trend id. | |
| page | No | Page number (1-1000). Default: 1. A full page may be followed by an empty page when the list ends exactly at a page boundary. | |
| slug | No | Trend slug to look up, e.g. `ghost-in-the-machine-ai-legacy-code`. | |
| limit | No | Rows per page (1-1000). Default: 30. A page is the same price at any size. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| include | No | `articles` adds a page of the trend's posts (`page` and `limit` apply to them). | |
| 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. |