Skip to main content
Glama
metricool

mcp-metricool

Official
by metricool

get_googleads_campaigns

Retrieve Google Ads campaign data from your Metricool account for a specified date range and blog ID using the MCP server mcp-metricool.

Instructions

Get the list of Google 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 that implements the core logic of the 'get_googleads_campaigns' tool. It is decorated with @mcp.tool(), which registers it with the FastMCP server. The function fetches Google Ads campaigns data from the Metricool API using a GET request based on the provided init_date, end_date, and blog_id parameters.
    @mcp.tool()
    async def get_googleads_campaigns(init_date: str, end_date: str, blog_id: int) -> str | list[dict[str, Any]]:
        """
        Get the list of Google 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/adwords/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 Google Ads Campaigns")
    
        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. It states it 'gets' data, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, pagination, error handling, or what happens if dates are invalid. 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 with the main purpose in the first sentence. The 'Args' section efficiently lists parameters with brief explanations. No wasted sentences, though it could be slightly more structured (e.g., bullet points).

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 explains parameters but lacks behavioral context (e.g., data format, error cases) and doesn't describe return values, which is critical for a data-fetching tool with no output schema provided.

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 meaning by explaining all 3 parameters: 'init date' and 'end date' define the period with format YYYYMMDD, and 'blog id' specifies the Metricool brand account. This clarifies purpose beyond the bare schema, though it doesn't detail constraints like valid date ranges.

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 Google Ads Campaigns from your Metricool account'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_facebookads_campaigns' or 'get_tiktokads_campaigns', which would require mentioning it's specifically for Google Ads campaigns.

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_facebookads_campaigns' for Facebook Ads or 'get_tiktokads_campaigns' for TikTok Ads, nor does it specify prerequisites or context for selecting this tool over others.

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