Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dev.to posts

dev_to_articles_search
Read-onlyIdempotent

Search Dev.to posts by keyword to find relevant articles, returning a paginated result list you can filter by recency and dedupe by post id.

Instructions

Search Dev.to posts by keyword. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_articles_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoOnly posts from the last N days.
pageNoPage number (1-1000). Default: 1. Live feeds move as posts are published, so a later page can repeat rows from an earlier one; dedupe by `id`.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
queryYesRequired. Search text. Matches post titles, tags and bodies.
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.4/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 'requires query' and 'returns a list', saying nothing about the live-feed pagination drift, dedupe-by-id requirement, or the conversation_id handshake that the schema documents. Useful but thin for a read tool with an open-world source.

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 short sentences with the required parameter front-loaded and no wasted wording. The parenthetical 'use page when paginated' is slightly vague but earns its place as a nudge toward iteration.

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?

With 7 parameters, three required meta-parameters (context, llm_model, conversation_id) and no output schema, the description covers only the search surface. The schema compensates for parameter detail, but the description leaves return shape and the required call-sequence behavior unaddressed, so an agent gets an incomplete picture from the description alone.

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 the schema already explains query, page, limit, top, and the meta-parameters in detail. The description merely restates that query is required and page exists, adding no syntax, format, or matching-scope detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb and resource: search Dev.to posts by keyword. This implicitly distinguishes it from dev_to_articles_list, but the description never names that sibling or explicitly says how the two differ, so an agent must infer the boundary.

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?

The tool's context of use (keyword retrieval) is implied by 'by keyword', and 'use page when paginated' hints at iteration. There is no explicit when-to-use versus dev_to_articles_list, no note that search is for topical text matching while list is for browsing, and no exclusions.

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