Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_shopping_feed_status

Verify your Merchant Center feed connection to ensure products flow from Merchant Center to Google Ads shopping campaigns.

Instructions

Check the status of your Google Merchant Center feed connection.

Verifies that your Merchant Center account is properly linked to Google Ads and that products can flow from Merchant Center to your shopping campaigns.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) merchant_center_id: Your Merchant Center account ID

Returns: Merchant Center feed status

Example: google_ads_shopping_feed_status( customer_id="1234567890", merchant_center_id="123456789" )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
merchant_center_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler that checks Google Merchant Center feed status. Decorated with @mcp.tool() and registered via register_shopping_pmax_tools(). It calls ShoppingPMaxManager.get_shopping_feed_status() and formats the result.
    def google_ads_shopping_feed_status(
        customer_id: str,
        merchant_center_id: str
    ) -> str:
        """Check the status of your Google Merchant Center feed connection.
    
        Verifies that your Merchant Center account is properly linked to Google Ads
        and that products can flow from Merchant Center to your shopping campaigns.
    
        Args:
            customer_id: Google Ads customer ID (10 digits, no hyphens)
            merchant_center_id: Your Merchant Center account ID
    
        Returns:
            Merchant Center feed status
    
        Example:
            google_ads_shopping_feed_status(
                customer_id="1234567890",
                merchant_center_id="123456789"
            )
        """
        with performance_logger.track_operation('shopping_feed_status', customer_id=customer_id):
            try:
                client = get_auth_manager().get_client()
                shopping_manager = ShoppingPMaxManager(client)
    
                result = shopping_manager.get_shopping_feed_status(
                    customer_id=customer_id,
                    merchant_center_id=merchant_center_id
                )
    
                audit_logger.log_api_call(
                    customer_id=customer_id,
                    operation='shopping_feed_status',
                    status='success'
                )
    
                output = f"# 📊 Merchant Center Feed Status\n\n"
                output += f"**Merchant Center ID**: {result['merchant_center_id']}\n"
                output += f"**Status**: {result['status']}\n\n"
    
                if result['status'] == 'NOT_LINKED':
                    output += "❌ **Merchant Center account is not linked**\n\n"
                    output += "**To link your Merchant Center account**:\n"
                    output += "1. Go to Google Ads → Tools & Settings → Linked accounts\n"
                    output += "2. Find Google Merchant Center and click 'Link'\n"
                    output += "3. Approve the link request in Merchant Center\n"
                elif result['status'] == 'ENABLED':
                    output += "✅ **Merchant Center is linked and active**\n\n"
                    output += f"**Link ID**: {result.get('link_id', 'N/A')}\n\n"
                    output += "Your products are ready to use in shopping campaigns!\n"
                else:
                    output += f"⚠️ **Status**: {result['message']}\n\n"
                    output += "Check your Merchant Center account for issues.\n"
    
                return output
    
            except Exception as e:
                error_msg = ErrorHandler.handle_error(e, context="shopping_feed_status")
                return f"❌ Failed to get feed status: {error_msg}"
  • The business logic that queries Google Ads API for merchant center link status using a GAQL query on the merchant_center_link table. Returns status (e.g. NOT_LINKED, ENABLED), merchant_center_id, and link_id.
    def get_shopping_feed_status(
        self,
        customer_id: str,
        merchant_center_id: str
    ) -> Dict[str, Any]:
        """Check Merchant Center feed status.
    
        Args:
            customer_id: Customer ID (without hyphens)
            merchant_center_id: Merchant Center ID
    
        Returns:
            Feed status information
        """
        ga_service = self.client.get_service("GoogleAdsService")
    
        query = f"""
            SELECT
                merchant_center_link.id,
                merchant_center_link.merchant_center_id,
                merchant_center_link.status
            FROM merchant_center_link
            WHERE merchant_center_link.merchant_center_id = {merchant_center_id}
        """
    
        response = ga_service.search(customer_id=customer_id, query=query)
        results = list(response)
    
        if not results:
            return {
                'status': 'NOT_LINKED',
                'message': 'Merchant Center account not linked',
                'merchant_center_id': merchant_center_id
            }
    
        link = results[0].merchant_center_link
    
        return {
            'status': link.status.name,
            'merchant_center_id': str(link.merchant_center_id),
            'link_id': str(link.id),
            'message': f'Merchant Center account is {link.status.name}'
        }
  • The registration function that contains @mcp.tool() decorators for all shopping/PMax tools, including google_ads_shopping_feed_status.
    def register_shopping_pmax_tools(mcp):
  • Module-level registration entry in the _TOOL_MODULES list that maps the 'shopping_pmax' module to its registration function.
    ("shopping_pmax", "tools.shopping_pmax.mcp_tools_shopping_pmax", "register_shopping_pmax_tools"),
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only check ('verifies', 'checks') without explicitly stating it's non-destructive. Sufficient but could be more explicit.

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 concise with a clear Args/Returns/Example structure. No redundant text, and the key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema, the description doesn't need to detail return values. It covers purpose, parameters, and an example. Could mention error scenarios but is complete enough for a status check tool.

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 schema has no descriptions, but the description adds context for both parameters: customer_id format (10 digits, no hyphens) and merchant_center_id as 'Your Merchant Center account ID'. This adds value beyond bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Check the status of your Google Merchant Center feed connection' and elaborates on verifying the link and product flow. This distinguishes it from sibling tools like google_ads_shopping_performance.

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 explains what the tool does but does not provide explicit guidance on when to use it versus alternatives or when not to use it. No exclusions or context for better decisions.

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

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/johnoconnor0/google-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server