Connect Google Ads to VS Code

Inspect campaigns, ad groups, keywords, and performance. Add Toolspoke to VS Code once and it can use 14 Google Ads actions. Your Google Ads credential stays in Toolspoke, and you choose which actions VS Code may call.

Set it up in VS Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to VS Code

    .vscode/mcp.json, or the MCP: Add Server command

    { "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

    Approve the authorization request when VS Code opens it.

  2. Install Google Ads and connect it

    Add Google Ads to a project in your Toolspoke workspace.

    Press connect and sign in to Google Ads. Toolspoke keeps the token encrypted and refreshes it when it expires, so there is nothing to copy and nothing to rotate by hand.

  3. Choose what VS Code may do

    All 14 actions only read, and any of them can be switched off for a project.

What you can ask VS Code for

A few of the Google Ads actions that only read, so they are safe to try first.

  • List every Google Ads account the connected OAuth user can reach
  • List the accounts sitting under a manager (MCC) account, including nested levels
  • Account spend and performance broken down by day
  • Return per-campaign performance for a date range, sorted by spend

What VS Code can do in Google Ads

14 actions read.

Reads

  • List accessible customers

    List every Google Ads account the connected OAuth user can reach. Call this first when you do not know which customer ID to work with; manager accounts are included, so follow up with list_child_accounts to reach the accounts that actually hold campaigns.

  • List child accounts

    List the accounts sitting under a manager (MCC) account, including nested levels. Use it to turn a manager customer ID from list_accessible_customers into the client customer IDs that hold campaigns and spend.

  • Account performance

    Return account-level spend and performance totals (impressions, clicks, CTR, cost, conversions) for one customer over a date range. Set segment_by_date to get a day-by-day series instead of a single total. Cost values are micros: divide by 1,000,000 for the account currency.

  • Account performance daily

    Account spend and performance broken down by day. Use account_performance for a single total over the range. Cost values are micros: divide by 1,000,000.

  • List campaigns

    List campaigns in an account with their structure, status, channel type, bidding strategy, flight dates and daily budget. Returns campaigns regardless of whether they have recent traffic; use campaign_metrics when you need performance numbers.

  • Campaign metrics

    Return per-campaign performance for a date range, sorted by spend. Use this for 'which campaigns are spending / converting' questions. Campaigns with no delivery in the window are omitted. Cost fields are micros (divide by 1,000,000).

  • Campaign metrics daily

    Campaign performance broken down by day. Use campaign_metrics for one row per campaign over the range. Cost values are micros: divide by 1,000,000.

  • List ad groups

    List ad groups with their campaign, status, type and CPC bid, optionally scoped to one campaign. Use it to drill from a campaign into the ad groups that hold keywords and ads.

  • Search keywords

    Find keywords in an account by text, ad group or campaign, returning match type, status, bid and whether the keyword is a negative. This is structural, it lists keywords even if they had no traffic. Use keyword_metrics for performance.

  • Keyword metrics

    Return keyword-level performance (impressions, clicks, CTR, cost, conversions) for a date range, sorted by spend. Use it to find the keywords driving or wasting budget. Cost fields are micros.

  • Search terms report

    Return the actual user queries that triggered ads over a date range, with the keyword that matched and the resulting cost and conversions. Use it to spot irrelevant traffic worth adding as negative keywords, or new queries worth targeting.

  • List ads

    List the ads in an account or ad group with their type, status, final URLs and responsive search ad headlines and descriptions. Use it to review live ad copy before recommending changes.

  • List campaign budgets

    List the budgets configured in an account with their amount, delivery method and Google's recommended amount, plus which campaigns share each one. Read-only: this adapter never changes a budget.

  • Run gaql query

    Run an arbitrary read-only Google Ads Query Language (GAQL) statement, for reports the dedicated actions do not cover, geo, device, audience, asset, conversion_action, change_event and so on. The query must start with SELECT; a LIMIT is appended when you omit one. Prefer the dedicated actions when they fit.

Google Ads in VS Code: questions

Does VS Code see my Google Ads credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. VS Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Will 14 actions crowd VS Code's context?

No. Toolspoke shows VS Code five bridge tools, plus a guide where a toolkit has one, and VS Code searches for the Google Ads action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Where do the tools show up in VS Code?

In chat, in agent mode, which is where VS Code uses MCP servers. Add the block to .vscode/mcp.json for one workspace, or use the MCP: Add Server command.

What does it cost?

Tool calls are free on every plan, and a Google Ads call does not run in a sandbox, so it bills nothing.

Try Google Ads in VS Code

Free to start, and tool calls cost nothing on any plan.