Translated from the Japanese original on mureo.jp.
Yahoo! JAPAN Ads can also be driven by giving Claude Code instructions in plain language. The idea is no different from Google Ads. The difference is that there is still less tooling available for connecting to Yahoo! JAPAN Ads, and that is the biggest gap between the two. This article looks at how driving Yahoo! JAPAN Ads from Claude Code fits together, and where you are likely to catch.
The overall picture is in Can you automate ad ops with Claude Code?. The Google Ads side is in Driving Google Ads from Claude Code, and Meta Ads in Driving Meta Ads from Claude Code, and Amazon Ads in Driving Amazon Ads from Claude Code.
Search and display are separate systems
Yahoo! JAPAN Ads splits into Search Ads and Display Ads (Auction), and the consoles and APIs are separate. Unlike Google Ads, which is consolidated into one system, touching both on Yahoo! JAPAN Ads means dealing with two lineages. When driving them from Claude Code, keeping the two in mind as separate connections avoids confusion.
Connecting to Yahoo! JAPAN Ads through MCP
Claude Code on its own does not hold Yahoo! JAPAN Ads data. MCP (Model Context Protocol) sits in between and talks to the Yahoo! JAPAN Ads API. That structure is the same as Google Ads.
What differs is how you get the data. Rather than a query language like Google Ads’ GAQL, Yahoo! JAPAN Ads centers on submitting a report as a job, waiting for it to be produced, and then retrieving it. The numbers do not come straight back; you retrieve them after a beat. Claude Code can build the procedure including that wait, but the gap before a response is longer than with Google Ads.
Hurdles before you are connected
Applying for API access Using the Yahoo! JAPAN Ads API requires an application. It is the equivalent of Google Ads’ developer token, and approval can take time. Even though it is only the first time, this is where people stall, just as with Google Ads.
Understanding the account structure In Yahoo! JAPAN Ads, multiple accounts hang under a Business ID. Mix up which account you are operating on and you will apply changes to a different client. Checking the structure before you connect is safer.
There is little tooling that supports it This is the biggest difference from Google Ads. There is a reasonable amount of MCP tooling circulating for Google Ads, whereas the options for Yahoo! JAPAN Ads are limited. You either build the connection yourself or use a tool that supports Yahoo! JAPAN Ads. When something worked immediately on Google Ads but stalls on Yahoo! JAPAN Ads, this is usually the reason.
What you can do with Yahoo! JAPAN Ads once connected
- Pull search and display together: read the numbers split across two systems from a single instruction, and find CPA deterioration and waste.
- Automate the check: delegate everything from issuing the report job to retrieving it, and surface only what needs attention.
- Delegate trafficking and changes: creating ads, adjusting budgets, and revisiting keywords or placements can all be executed from your instructions.
Running it alongside Google Ads is where the payoff is
More effective than automating Yahoo! JAPAN Ads on its own is running it next to Google Ads in the same language. You can issue an instruction like “compare last week’s CPA on both platforms and pull back the budget on the worse one” across platforms at once. Work that meant opening two consoles and reconciling them is replaced by conversation. If you run search ads on both platforms, this is the biggest advantage.
Where people get stuck with Yahoo! JAPAN Ads
Build the report wait into your process Because it is job-based, there is a gap before the numbers come back. Rush ahead to the next decision and you may be acting on data that has not been retrieved yet. Building the procedure around the wait keeps things stable.
Metric definitions differ between platforms Even the same “conversion” may not count identically, or rest on the same measurement assumptions, across Yahoo! JAPAN Ads and Google Ads. When comparing across platforms, checking once whether the numbers rest on the same foundation avoids faulty comparisons.
Record the reason for changes The same as with Google Ads: if there is no log of the changes the AI made, you cannot explain the reasons later. The more platforms you handle, the more the design of your records pays off.
Sending the same data somewhere other than Claude Code
Claude Code is one destination for Yahoo! JAPAN Ads data, not the only one. Once API access is approved and the report job flow is working, the same retrieval can feed a Looker Studio dashboard, a BigQuery table, or a spreadsheet. The connection work does not change with the destination: the application, the authentication, submitting the report job, waiting for it, retrieving it. What changes is only what happens to the rows once they arrive.
Which destination suits which job is worth separating. Claude Code suits work where the question is not fixed in advance: looking into why CPA moved last week, executing a change once you have decided on it, and explaining afterwards why it was made. Looker Studio and BigQuery suit the opposite: a report whose shape is settled and repeats every week, numbers you want to keep for a year or more, and joining ad data with order or CRM data that never passes through the ad platform.
From where we sit building ad-ops tooling, teams usually end up with both rather than choosing. One connection reads Yahoo! JAPAN Ads and writes to wherever the numbers are needed: the warehouse for the long record, the dashboard for the standing report, and Claude Code for the questions that come up in between. Building a separate connection for each destination is where the maintenance cost accumulates, and on a platform where tooling is already scarce, that cost lands harder.
Summary
Connecting Yahoo! JAPAN Ads to Claude Code is not difficult, provided you can put the tooling together. The difference from Google Ads comes down to that tooling not yet being in place. And beyond the connection, the question is still how much to delegate and what to record. That is explored in Is it safe to hand ad ops to Claude Code?. We build mureo, which productizes multiple platforms including Google Ads and Yahoo! JAPAN Ads along with the design for delegation, so you can talk to us not only about how to connect but about how to structure operations.