Skip to main content
Glama
ferdousbhai

WSB Analyst MCP Server

fetch_batch_post_details

Retrieve details for multiple Reddit posts simultaneously to analyze WallStreetBets content for market insights.

Instructions

Fetch details for multiple posts efficiently.

Args:
    post_ids: List of Reddit post IDs

Returns:
    Dictionary with details for all requested posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idsYes

Implementation Reference

  • The core handler function for the 'fetch_batch_post_details' tool, registered via @mcp.tool() decorator. It processes a batch of post IDs by sequentially fetching details for each using 'fetch_post_details', aggregates the results, and provides progress updates via the Context if available.
    async def fetch_batch_post_details(post_ids: list[str], ctx: Context = None) -> dict:
        """
        Fetch details for multiple posts efficiently.
    
        Args:
            post_ids: List of Reddit post IDs
    
        Returns:
            Dictionary with details for all requested posts
        """
        if not post_ids:
            return {"error": "No post IDs provided"}
    
        results = {}
        total = len(post_ids)
    
        for i, post_id in enumerate(post_ids):
            if ctx:
                await ctx.report_progress(i, total)
    
            detail = await fetch_post_details(post_id)
            results[post_id] = detail
    
        if ctx:
            await ctx.report_progress(total, total)
    
        return {
            "count": len(results),
            "posts": results
        }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states it fetches details efficiently but doesn't disclose rate limits, authentication needs, error handling, or what happens if some post IDs are invalid. This is inadequate for a tool with no annotation coverage.

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 brief with three sentences that are front-loaded (purpose first, then args, then returns). No wasted words, though the structure could be slightly improved by integrating usage context.

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?

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on return format (beyond 'dictionary'), error cases, performance characteristics, and differentiation from siblings, making it insufficient for reliable tool selection.

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 0%, but the description adds basic meaning by specifying 'post_ids' as 'List of Reddit post IDs'. However, it doesn't clarify format constraints, size limits, or provide examples, leaving significant gaps in parameter understanding.

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 with specific verbs ('fetch details') and resource ('multiple posts'), and mentions efficiency. However, it doesn't distinguish this batch operation from the sibling 'fetch_post_details' tool, which likely fetches single posts.

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 about when to use this tool versus alternatives like 'fetch_post_details' or 'fetch_detailed_wsb_posts'. The description mentions efficiency for multiple posts but doesn't specify thresholds 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/ferdousbhai/wsb-analyst-mcp'

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