Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to trends

dev_to_trends_list
Read-onlyIdempotent

Fetches trending Dev.to topics with optional page and limit parameters, helping you discover current developer discussions and content ideas.

Instructions

List the topics trending on Dev.to. Optional inputs: page and limit. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_trends_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-1000). Default: 1. A full page may be followed by an empty page when the list ends exactly at a page boundary.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only a light pagination note ("Returns a list (use page when paginated)"), which is useful but thin; it says nothing about ordering, freshness, or whether results are cached.

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

Conciseness4/5

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

Three short sentences, front-loaded with the purpose, with no filler. The trailing parenthetical about pagination is slightly redundant given the schema's page description but not wasteful.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with a fully described schema and no output schema, the essentials are present. However, it never clarifies what a "trending topic" is (tag? article?) or how results differ from the sibling dev_to_trend_get, leaving a real ambiguity for an agent choosing between them.

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 page, limit, context, llm_model, and conversation_id are all documented in the schema with defaults and ranges. The description merely restates that page and limit are optional, adding no syntax or behavioral meaning beyond the structured fields.

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?

"List the topics trending on Dev.to" gives a specific verb (list) and resource (trending topics), scoped to a named platform. An agent can distinguish it from generic trend tools, though it never contrasts itself with the sibling dev_to_trend_get, which sounds adjacent.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is offered; the only directive is the parenthetical "use page when paginated," which is about mechanics rather than tool selection. The agent must infer on its own whether to call this versus dev_to_trend_get or the google_trends_* family.

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