Skip to main content
Glama

search_articles

Find articles on Dev.to by entering search terms to locate relevant content for research, learning, or content discovery.

Instructions

Search for articles on Dev.to

Args:
    query: Search term to find articles
    page: Page number for pagination (default: 1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
pageNo

Implementation Reference

  • server.py:48-66 (handler)
    The handler function for the 'search_articles' tool. It is decorated with @mcp.tool(), which registers it in the FastMCP server. Fetches paginated articles from Dev.to API, filters them client-side by searching query in title or description, limits to 10, and formats output using format_articles helper.
    @mcp.tool()
    async def search_articles(query: str, page: int = 1) -> str:
        """
        Search for articles on Dev.to
        
        Args:
            query: Search term to find articles
            page: Page number for pagination (default: 1)
        """
        articles = await fetch_from_api("/articles", params={"page": page})
        
        filtered_articles = [
            article for article in articles 
            if query.lower() in article.get("title", "").lower() or 
               query.lower() in article.get("description", "").lower()
        ]
        
        return format_articles(filtered_articles[:10])
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions pagination ('page number for pagination'), it doesn't describe important behavioral traits like rate limits, authentication requirements, response format, error conditions, or what happens with empty results. For a search tool with zero annotation coverage, this is insufficient.

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?

The description is appropriately sized and front-loaded with the core purpose first. The two-sentence structure with clear parameter explanations is efficient, though the 'Args:' section formatting could be slightly cleaner. Every sentence earns its place by adding value.

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?

Given the tool's moderate complexity (search function with pagination), no annotations, and no output schema, the description is minimally adequate but has clear gaps. It covers the basic purpose and parameters but lacks crucial context about authentication, rate limits, response format, and when to use versus sibling tools. The absence of output schema means the description should ideally explain what the search returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context for both parameters beyond what the schema provides. For 'query', it explains it's a 'Search term to find articles' (schema just says 'Query'). For 'page', it clarifies it's for 'pagination' and provides the default value (schema only shows default:1). With 0% schema description coverage, the description effectively compensates by explaining parameter purposes.

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 clearly states the tool's purpose: 'Search for articles on Dev.to' - a specific verb ('Search') and resource ('articles on Dev.to'). It distinguishes itself from siblings like 'get_articles_by_tag' or 'get_latest_articles' by being a general search function, though this differentiation isn't explicitly stated.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention when this general search is preferable to more specific sibling tools like 'get_articles_by_tag' or 'get_latest_articles', nor does it provide any context about use cases or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Arindam200/devto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server