Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_facebookads_campaigns

Retrieve a list of Facebook Ads Campaigns from your Metricool account by specifying a date range and blog ID. Use this tool to organize and analyze campaign data efficiently.

Instructions

Get the list of Facebook Ads Campaigns from your Metricool account.

Args: init date: Init date of the period to get the data. The format is YYYYMMDD end date: End date of the period to get the data. The format is YYYYMMDD 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_facebookads_campaigns tool. It is decorated with @mcp.tool(), which handles registration and schema definition based on type hints and docstring. Fetches Facebook Ads campaigns data from Metricool API using a GET request.
    @mcp.tool()
    async def get_facebookads_campaigns(init_date: str, end_date: str, blog_id: int) -> str | list[dict[str, Any]]:
        """
        Get the list of Facebook Ads Campaigns from your Metricool account.
    
        Args:
         init date: Init date of the period to get the data. The format is YYYYMMDD
         end date: End date of the period to get the data. The format is YYYYMMDD
         blog id: Blog id of the Metricool brand account.
        """
    
        url = f"{METRICOOL_BASE_URL}/stats/facebookads/campaigns?start={init_date}&end={end_date}&blogId={blog_id}&userId={METRICOOL_USER_ID}&integrationSource=MCP"
    
        response = await make_get_request(url)
    
        if not response:
            return ("Failed to get Facebook Ads Campaigns")
    
        return response
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool retrieves data (implied read-only), but doesn't cover authentication needs, rate limits, pagination, error handling, or what the returned list includes (e.g., campaign details). This leaves significant gaps for a tool with 3 parameters and no output schema.

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. The 'Args' section is structured but could be more integrated; overall, it avoids unnecessary fluff and each part 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 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It covers parameter basics but lacks behavioral context (e.g., data format, errors), usage guidelines, and output details, 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.

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 3 parameters: 'init date' and 'end date' define a period with format YYYYMMDD, and 'blog id' specifies the Metricool brand account. This clarifies purpose beyond schema types, though it doesn't explain parameter interactions or constraints.

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 'Get the list of Facebook Ads Campaigns from your Metricool account,' which specifies the action (get/list), resource (Facebook Ads Campaigns), and source (Metricool account). It distinguishes from siblings like 'get_googleads_campaigns' by specifying the platform, but doesn't explicitly differentiate from other Facebook-related 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a Metricool account), exclusions, or comparisons to siblings like 'get_googleads_campaigns' or 'get_tiktokads_campaigns'. The description only states what it does, not when it's appropriate.

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