Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_facebook_posts

Retrieve Facebook posts from a Metricool brand account within a specified date range by providing the blog ID, start date, and end date in YYYY-MM-DD format.

Instructions

Get the list of Facebook 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 for the get_facebook_posts tool, decorated with @mcp.tool() which registers it with the MCP server. Fetches Facebook posts from the Metricool API endpoint using a GET request, with parameters for date range and blog ID. Returns the API response or an error message.
    @mcp.tool()
    async def get_facebook_posts(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
        """
        Get the list of Facebook 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/facebook?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 Facebook Posts")
    
        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 states the tool retrieves a list of posts but doesn't describe the return format (e.g., JSON structure, pagination), rate limits, authentication requirements, or error handling. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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: the first sentence states the purpose, followed by a structured 'Args:' section with parameter details. There's no wasted text, though the formatting (e.g., 'init date' vs. 'Init date') could be slightly more consistent. Every sentence adds value.

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 the complexity (3 parameters, no annotations, no output schema), the description is incomplete. It covers parameter semantics but lacks behavioral details (e.g., output format, error cases) and usage guidelines. For a tool that retrieves data over a date range, more context on what 'list' includes (e.g., post metadata, limits) would be helpful.

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 semantics for all three parameters beyond the schema (which has 0% description coverage). It explains that 'init date' and 'end date' define a period for data retrieval with format 'YYYY-MM-DD', and 'blog id' identifies the Metricool brand account. This compensates well for the schema's lack of descriptions, though it doesn't specify parameter constraints (e.g., date ranges, valid blog IDs).

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 Facebook Posts from your Metricool brand account.' It specifies the verb ('Get'), resource ('Facebook Posts'), and scope ('from your Metricool brand account'), which distinguishes it from generic Facebook tools. However, it doesn't explicitly differentiate from sibling tools like get_facebook_reels or get_facebook_stories, which target different Facebook content types.

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. It doesn't mention sibling tools like get_facebook_reels (for Facebook Reels) or get_facebook_stories (for Facebook Stories), nor does it specify prerequisites (e.g., authentication, brand account setup). The only implied context is needing a Metricool brand account, but this is minimal guidance.

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