Skip to main content
Glama

get_article_by_id

Retrieve a specific Dev.to article using its unique ID to access content details and information.

Instructions

Get a specific article by ID from Dev.to

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • server.py:40-45 (handler)
    Handler function for the 'get_article_by_id' tool. It fetches the article details from the Dev.to API using the provided ID and formats the output using format_article_details.
    @mcp.tool()
    async def get_article_by_id(id: str) -> str:
        """Get a specific article by ID from Dev.to"""
        article = await fetch_from_api(f"/articles/{id}")
        return format_article_details(article)
  • Helper function used by get_article_by_id to make API requests to Dev.to.
    async def fetch_from_api(path: str, params: dict = None) -> dict:
        """Helper function to fetch data from Dev.to API"""
        async with httpx.AsyncClient() as client:
            url = f"{BASE_URL}{path}"
            response = await client.get(url, params=params, timeout=10.0)
            response.raise_for_status()
            return response.json()
  • Helper function used by get_article_by_id to format the article details for output.
    def format_article_details(article: dict) -> str:
        """Format a single article with full details"""
        if not article:
            return "Article not found."
        
        title = article.get("title", "Untitled")
        author = article.get("user", {}).get("name", "Unknown Author")
        published_date = article.get("readable_publish_date", "Unknown date")
        body = article.get("body_markdown", "No content available.")
        tags = article.get("tags", "")
        
        result = f"# {title}\n\n"
        result += f"Author: {author}\n"
        result += f"Published: {published_date}\n"
        result += f"Tags: {tags}\n\n"
        result += "## Content\n\n"
        result += body
        
        return result
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify authentication requirements, rate limits, error handling, or what happens if the ID doesn't exist. For a 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple lookup tool and front-loads the essential information.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what data is returned, error conditions, or how this differs from similar sibling tools. The context demands more comprehensive guidance.

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?

The description mentions 'by ID' which aligns with the single 'id' parameter in the schema. However, with 0% schema description coverage, the description doesn't add any details about ID format, constraints, or examples. It provides basic mapping but minimal additional semantic value.

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 action ('Get') and resource ('a specific article by ID from Dev.to'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar siblings like 'get_article_details' or 'get_articles_by_tag', which likely also retrieve articles but through different mechanisms.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'get_article_details', 'get_articles_by_tag', and 'search_articles', there's no indication whether this tool is for retrieving a single known article ID versus other lookup methods.

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