Meta Muse for Google Merchant Center: Catch Disapproved Products Early

What Muse can see in Merchant Center

Through MCP Ads, Muse can list your Merchant Center accounts and client sub-accounts, and read a product status summary: counts of approved, pending and disapproved products per country and destination, with the most common issues. From there it can open a single product with its status, destinations and item-level issues, or render those issues the way Merchant Center shows them, with the explanation, the impact and the steps to fix.

It can also read account-level issues such as suspensions, policy warnings and missing settings; data sources (primary and supplemental feeds, API sources, promotion sources); promotions and their approval status; shipping settings, return policies and business information; which programs are enabled; whether the homepage is claimed; terms of service that are still pending; and top products by clicks, impressions or conversions. The Merchant Center MCP page lists the full set.

Connect it in 30 seconds

Muse has no connector settings screen, so there is nothing to click through. You send it one message that says where MCP Ads is. Muse replies with a sign-in link, you approve it, and Muse tests the tools and saves them for later conversations and scheduled checks. Connect Merchant Center under Connections in the MCP Ads dashboard. It shares one Google sign-in with Google Ads, GA4 and Search Console, with its own permission.

If Muse asks for a credential instead of sending a link, create an API key in the MCP Ads dashboard under Connect MCP → API keys and paste it into Muse's secure credential prompt, not into the chat. If it asks for a client ID or client secret, leave both empty. MCP Ads is not in Muse's connector directory yet, so this message is the way in; the Muse setup page has the same steps. Paste these lines into Muse as a single message:

• Add my MCP Ads connector: https://mcp-ads.com/mcp-slim
• Setup: standard MCP over streamable HTTP with OAuth. Send me the sign-in link and I will approve it. Keep one session (Mcp-Session-Id) for all calls.
• Skill: save one so every question about my ads, analytics or SEO goes through MCP Ads tools first.
• Once you are in, show my product status summary and the three issues affecting the most products.

The approval check, on a schedule

The most useful routine is short: every morning, or every Monday for a small catalogue, ask Muse for the status summary and to report only if disapprovals rose or a new issue appeared. When one did, have it open two or three affected products and read Google's fix steps, so the note you get says what to change, not just that something is wrong.

Order the work by revenue. Muse can pull Merchant Center product performance, and, if Google Ads is connected too, Shopping performance by product, so a disapproved best-seller comes before a disapproved item that never sold.

Prompts that work

Name the account (and country, if you sell in several), and ask for the fix steps, not just the issue name.

• Show approved, pending and disapproved products for the US on Shopping ads, with the top five issues.
• For the ten disapproved products with the most clicks last month, show Google's explanation and fix for each.
• Are there any account-level issues or terms of service I still need to accept?
• List my data sources and when each feed was last fetched, then fetch the main feed now.
• Which promotions are pending or rejected, and why?
• Every morning at 7, check the product status summary and message me only if disapprovals rose since yesterday, with the new issue and three example products.
• Every Monday at 9, list the top 20 products by clicks and flag any that are not approved in every country I sell in.

What Muse should always confirm with you

Muse can change specific attributes of a product while leaving the rest untouched, set store and regional prices and availability, fetch a scheduled feed now instead of waiting, create promotions, and update shipping settings and return policies. Several Merchant Center actions are marked in MCP Ads to be confirmed with you first, because they change whether anything serves: disabling a program such as free listings or Shopping ads, unclaiming the homepage, deleting a data source (which removes products only it supplies), accepting terms of service, adding or removing users, and deleting an account, which cannot be undone.

Treat a scheduled Merchant Center check as read-and-report, and make fixes in a separate request you can see. Muse sees only the Merchant Center accounts your Google login can reach and that you connected in MCP Ads.

Pitfalls and honest limits

Fix data at its source. A product often comes from a feed file or a store plugin, and a fix made only through the API may be replaced when that source next updates. Where the problem is in the feed, change the feed. Changes also take a few minutes to show in the product status, and Google reviews some changes before a product serves again, so check the next day rather than immediately.

Every tool call counts against your Muse usage; a product-by-product sweep of a large catalogue is many calls, so start from the summary and drill into the products that matter. MCP Ads has a 7-day free trial, then $49/month flat; see pricing and the Merchant Center setup docs.