Skip to main content
Glama

Visibility Genies

Read Google Ads search terms

get_google_ads_search_terms
Read-only

The connected Google Ads account's paid search terms for a date range, from what the daily pull stored: impressions, clicks, cost, conversions, conversion value and cost per conversion, most spend first, with each term's organic clicks, impressions and average position from Search Console over the same days (null where Search Console has none for the term; organicState says whether it was read). Also the account's campaign spend (accountSpend) and, for Performance Max campaigns, Google's Performance Max search categories (searchCategories): groups of similar searches with impressions, clicks and conversions but no cost. Money is in the account's currency (currencyCode). Days are in the account's time zone; at most 90 days. Read-only; uses no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_google_ads_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 100, max 500).
endDateNoLast day (YYYY-MM-DD). Use with startDate. Without both, the last 30 stored days. At most 90 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the Ads account's time zone). Use with endDate.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
noteNo
rowsNo
reasonNo
endDateNo
hasMoreNo
messageNo
failedAtNo
rowCountNo
startDateNo
connectUrlNo
accountNameNo
accountSpendNo
currencyCodeNo
organicStateNo
storedThroughNo
searchCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and non-destructive, yet the description still adds substantial behavior: data comes from a stored daily pull rather than a live API call, organic fields are null where Search Console has no data and organicState signals whether the lookup ran, money is in the account currency, days are in the account time zone, and no credits are consumed. These are exactly the traits an agent cannot get from the structured fields.

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?

It is one dense paragraph with no filler or repeated sentences, and the most decision-relevant facts (source of data, the organic join, currency/time zone, 90-day cap, read-only) are front-loaded. It is long largely because it enumerates return metrics that a separate output schema already covers, which is the main efficiency cost.

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

Completeness5/5

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

For a four-parameter read tool with an output schema and read-only annotations, everything an agent needs to call it correctly is present: required project scoping is implicit in the schema, the default window, the 90-day maximum, null semantics for organic fields, and the currency/time-zone interpretation of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the last-30-days default and the 90-day cap, so the baseline is 3. The description reinforces the time-zone interpretation of the date range but adds nothing about the limit parameter or date-pairing behavior beyond what the schema already states.

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 names a specific resource (paid search terms for the connected Google Ads account) and its key twist: paid metrics joined with Search Console organic data plus account-level campaign spend and Performance Max search categories. It does not explicitly distinguish itself from close siblings such as get_google_ads_terms_without_ranking or get_search_console_performance, so it stops short of a 5.

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?

There is no explicit 'use this when / use X instead' guidance and no named alternative, even though the sibling list contains clearly overlapping tools. Usage is only implied: it is read-only, uses no credits, and caps the window at 90 days, which the reader must piece together into a selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources