Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dev.to profile

dev_to_user_profile_get
Read-onlyIdempotent

Fetch 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

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Dev.to username, e.g. `ben`. A profile URL such as https://dev.to/ben is also accepted.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral fact that the response aggregates multiple content types (counts, badges, work, skills, repos). It says nothing about error handling for an unknown username, rate limits, or response size, which are the remaining behavioral unknowns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the returned-data inventory front-loaded ahead of the parameter note. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly compensates by listing what the profile contains, and annotations cover the safety semantics. Completeness is only slightly undercut by the absence of failure-mode and sibling-selection guidance, which matters given a near-identically named dev_to_user_get.

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 description coverage is 100%, so all four parameters are fully documented in the schema, including the username pattern and the accepted profile-URL form. The description only restates that `username` is required, adding no syntax or format meaning beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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?

The description uses a specific verb ('Get') plus resource ('Dev.to profile page') and enumerates the payload: post, comment and tag counts, badges, work, skills and GitHub repositories. That is far more informative than the bare title. It stops short of differentiating itself from the closely named sibling dev_to_user_get, so an agent cannot tell from this text which of the two to prefer.

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

Usage Guidelines3/5

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

Usage is only implied by the purpose: fetch a full profile for a given username. There is no explicit statement of when to choose this over dev_to_user_get, no exclusions, and no note about behavior for nonexistent users. The one concrete constraint, 'Requires `username`', is a prerequisite but is already enforced by the schema's required list.

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