Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dev.to trend

dev_to_trend_get
Read-onlyIdempotent

Fetches 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

NameRequiredDescriptionDefault
idNoNumeric trend id.
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.
slugNoTrend slug to look up, e.g. `ghost-in-the-machine-ai-legacy-code`.
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.
includeNo`articles` adds a page of the trend's posts (`page` and `limit` apply to them).
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only that results can carry the trend's top posts, without covering pagination behavior or anything about the required analytics parameters (context, llm_model, conversation_id) that shape the call flow.

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?

Two compact sentences with the core action front-loaded and no filler. The second sentence is a bare list of parameter names that does little work, but nothing is verbose or buried.

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 an 8-parameter read tool with no output schema, the description covers the basic action but says nothing about the shape of the returned trend or its posts, nor about the special first-call conversation_id flow. Rich schema text compensates partially, so this is adequate but with clear gaps.

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 every parameter including context, llm_model and conversation_id is already documented in the schema, which sets the baseline at 3. The description merely repeats five parameter names with no added meaning, and it omits three of the eight parameters entirely.

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 states a specific verb and resource — 'Get a trending Dev.to topic' — plus the notable scope that it can include the trend's top posts. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling dev_to_trends_list, leaving the agent to infer single-item vs list behavior.

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?

The description mentions that inputs are 'optional' but gives no when-to-use context, no guidance on choosing between `id` and `slug` for lookup, and no indication of when to add `include: articles`. No alternative tool is named even though dev_to_trends_list is a plausible competitor.

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