Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_bluesky_posts

Retrieve Bluesky posts from your Metricool brand account within a specified date range by providing the init date, end date, and blog ID for organized data access.

Instructions

Get the list of Bluesky Posts from your Metricool brand account.

Args: init date: Init date of the period to get the data. The format is YYYY-MM-DD end date: End date of the period to get the data. The format is YYYY-MM-DD blog id: Blog id of the Metricool brand account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blog_idYes
end_dateYes
init_dateYes

Implementation Reference

  • Handler function decorated with @mcp.tool() that implements the get_bluesky_posts tool. It fetches Bluesky posts from the Metricool API for a given date range and blog ID, using make_get_request utility. The function signature and docstring define the input schema and description.
    @mcp.tool()
    async def get_bluesky_posts(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
        """
        Get the list of Bluesky Posts from your Metricool brand account.
    
        Args:
         init date: Init date of the period to get the data. The format is YYYY-MM-DD
         end date: End date of the period to get the data. The format is YYYY-MM-DD
         blog id: Blog id of the Metricool brand account.
        """
    
        url = f"{METRICOOL_BASE_URL}/v2/analytics/posts/bluesky?from={init_date}T00%3A00%3A00&to={end_date}T23%3A59%3A59&blogId={blog_id}&userId={METRICOOL_USER_ID}&integrationSource=MCP"
    
        response = await make_get_request(url)
    
        if not response:
            return ("Failed to get Bluesky Posts")
    
        return response
  • Utility function used by the handler to make authenticated GET requests to the Metricool API.
    async def make_get_request(url: str) -> dict[str, Any] | None:
        """Make a get request to the Metricool API with proper error handling."""
        headers = {
            "X-Mc-Auth": METRICOOL_USER_TOKEN,
        }
        async with httpx.AsyncClient() as client:
            try:
                response = await client.get(url, headers=headers, timeout=30.0)
                response.raise_for_status()
                return response.json()
            except Exception:
                return None
  • Server file that imports the mcp instance from tools (where tools are registered via @mcp.tool() decorators) and runs the MCP server.
    from .tools import tools
    
    mcp = tools.mcp
    
    if __name__ == "__main__":
        # Initialize and run the server
        mcp.run(transport='stdio')
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation ('Get') but doesn't cover authentication needs, rate limits, pagination, error handling, or what 'list' entails (e.g., format, completeness). This leaves significant gaps for a tool with parameters.

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, followed by parameter details. Each sentence adds value without redundancy, though the parameter explanations could be slightly more integrated into the flow.

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 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It covers parameter basics but lacks behavioral context, output details, and usage guidelines, making it inadequate for reliable tool invocation.

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%, so the description must compensate. It adds meaning by explaining each parameter's purpose and date formats, covering all 3 parameters. However, it doesn't detail constraints like valid date ranges or blog_id sourcing, leaving some semantic gaps.

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 verb ('Get') and resource ('list of Bluesky Posts from your Metricool brand account'), making the purpose evident. It distinguishes from siblings by specifying Bluesky posts, but doesn't explicitly contrast with similar tools like get_x_posts or get_instagram_posts beyond the platform name.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, appropriate contexts, or comparisons with sibling tools like get_x_posts or get_analytics, leaving the agent without usage direction.

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

Related 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/metricool/mcp-metricool'

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