Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_network_competitors_posts

Retrieve competitor posts from specified networks within a defined date range to analyze and draw insights for your brand strategy. Supports Twitter, Facebook, Instagram, YouTube, Twitch, and Bluesky.

Instructions

Get the list of posts from your competitors from your Metricool brand account. Add interesting conclusions for my brand about my competitors and analyze their posts.

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 network: Network to retrieve the posts. The format is "twitter", "facebook", "instagram", "youtube", "twitch" and "bluesky". Only these are accepted. blog id: Blog id of the Metricool brand account. limit: Limit of posts of competitors. By default = 50 timezone: Timezone of the post. The format is "Europe%2FMadrid". Use the timezone of the user extracted from the get_brands tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blog_idYes
end_dateYes
init_dateYes
limitYes
networkYes
timezoneYes

Implementation Reference

  • The handler function for the get_network_competitors_posts tool. It is decorated with @mcp.tool(), which registers it automatically with FastMCP using the function name as the tool name. The function fetches competitors' posts from the Metricool API, handling Instagram by combining publications and reels data.
    @mcp.tool()
    async def get_network_competitors_posts(network: str, init_date: str, end_date: str, blog_id: int, limit: int, timezone: str) -> str | dict[str, Any]:
        """
        Get the list of posts from your competitors from your Metricool brand account.
        Add interesting conclusions for my brand about my competitors and analyze their posts.
    
        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
         network: Network to retrieve the posts. The format is "twitter", "facebook", "instagram", "youtube", "twitch" and "bluesky". Only these are accepted.
         blog id: Blog id of the Metricool brand account.
         limit: Limit of posts of competitors. By default = 50
         timezone: Timezone of the post. The format is "Europe%2FMadrid".  Use the timezone of the user extracted from the get_brands tool.
        """
        if(network=="instagram"):
            url = f"{METRICOOL_BASE_URL}/v2/analytics/competitors/{network}/publications?from={init_date}T00%3A00%3A00&to={end_date}T23%3A59%3A59&blogId={blog_id}&userId={METRICOOL_USER_ID}&limit={limit}&timezone={timezone}&integrationSource=MCP"
            response_pub = await make_get_request(url)
            url = f"{METRICOOL_BASE_URL}/v2/analytics/competitors/{network}/publications?from={init_date}T00%3A00%3A00&to={end_date}T23%3A59%3A59&blogId={blog_id}&userId={METRICOOL_USER_ID}&limit={limit}&timezone={timezone}&integrationSource=MCP"
            response_reels = await make_get_request(url)
            response={"publications":response_pub, "reels":response_reels}
        else:
            url = f"{METRICOOL_BASE_URL}/v2/analytics/competitors/{network}/posts?from={init_date}T00%3A00%3A00&to={end_date}T23%3A59%3A59&blogId={blog_id}&userId={METRICOOL_USER_ID}&limit={limit}&timezone={timezone}&integrationSource=MCP"
    
            response = await make_get_request(url)
    
        if not response:
            return ("Failed to get competitors")
    
        return response
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. It mentions retrieving and analyzing posts, but does not specify whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. The description adds minimal behavioral context beyond the basic action, leaving significant gaps for an AI agent.

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 a clear 'Args:' section detailing parameters. Each sentence adds value, though the analysis part ('Add interesting conclusions...') could be more integrated. Overall, it's efficient with minimal waste.

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 6 parameters with 0% schema coverage and no output schema, the description does well on parameter semantics but lacks behavioral details (e.g., output format, error handling). It's complete enough for basic usage but insufficient for full transparency, especially as a data retrieval tool with no annotations.

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

Parameters5/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 provides detailed semantics for all 6 parameters: formats for dates (YYYY-MM-DD), network options (e.g., 'twitter', 'facebook'), blog id context, limit default (50), and timezone format and source ('Use the timezone of the user extracted from the get_brands tool'). This adds substantial meaning beyond the bare schema.

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: 'Get the list of posts from your competitors from your Metricool brand account' and adds 'Add interesting conclusions for my brand about my competitors and analyze their posts.' This specifies the verb ('get'), resource ('posts from competitors'), and context ('Metricool brand account'), but does not explicitly differentiate it from sibling tools like 'get_network_competitors' or network-specific tools (e.g., 'get_facebook_posts').

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 description implies usage context by mentioning 'competitors' and 'Metricool brand account,' suggesting it's for competitive analysis. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_network_competitors' (which might provide different data) or network-specific tools. No exclusions or prerequisites are stated, leaving usage somewhat ambiguous.

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