Get Dev.to profile
dev_to_user_profile_getFetch a Dev.to user's profile data—post, comment, and tag counts, badges, work, skills, and GitHub repositories—using a username or profile URL.
Instructions
Get a Dev.to profile page: post, comment and tag counts, badges, work, skills and GitHub repositories. Requires username.
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": {
"username": "<username>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "dev_to_user_profile_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| username | Yes | Required. Dev.to username, e.g. `ben`. A profile URL such as https://dev.to/ben is also accepted. | |
| 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. |