Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_facebook_reels

Retrieve a list of Facebook Reels from your Metricool account by specifying a date range and blog ID for targeted performance insights.

Instructions

Get the list of Facebook Reels from your Metricool 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

  • The handler function for the 'get_facebook_reels' tool. Decorated with @mcp.tool() for registration. Fetches Facebook Reels data from the Metricool API using a GET request. Includes input parameters, docstring schema description, and logic to handle response or error.
    @mcp.tool()
    async def get_facebook_reels(init_date: str, end_date: str, blog_id: int) -> str | dict[str, Any]:
        """
        Get the list of Facebook Reels from your Metricool 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/reels/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 Reels")
    
        return response
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a list, implying a read-only operation, but lacks details on permissions, rate limits, pagination, error handling, or response format. For a tool with three required parameters and no annotation coverage, this is a significant gap in transparency.

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 clearly, followed by a structured Args section. There's no wasted text, though the formatting as a code block might be slightly verbose. Every sentence earns its place by adding value.

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 the tool's moderate complexity (3 required parameters, no output schema, no annotations), the description is partially complete. It covers parameter semantics well but lacks behavioral details like response format, error cases, or usage context. Without annotations or output schema, the agent has incomplete information for reliable invocation.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaningful context for all three parameters: it explains that init_date and end_date define a period for data retrieval with specific format (YYYY-MM-DD), and blog_id refers to a Metricool brand account. This goes beyond the schema's basic titles and types, providing essential usage semantics.

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 the list of') and resource ('Facebook Reels from your Metricool account'), which distinguishes it from siblings like get_facebook_posts or get_instagram_reels. However, it doesn't explicitly differentiate from other list-fetching tools like get_analytics or get_metrics beyond the resource 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a Metricool account with Facebook integration), exclusions, or comparisons to similar tools like get_facebook_posts or get_instagram_reels, leaving the agent to infer usage from the name alone.

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