Skip to main content
Glama

Visibility Genies

Read paid terms without a ranking

get_google_ads_terms_without_ranking
Read-only

The connected Google Ads account's paid search terms that the site has no organic position for, most spend first, with cost and conversions for a date range, and each term's organic clicks, impressions and Search Console average position where Search Console has them (organicState says whether it was read): the spend organic work could replace. Positions come from the project's rank tracking of its own site, read from saved checks; nothing is bought or fetched. tracked: true means the last check did not find the site; tracked: false means the term is not tracked, so its position is unknown (add it to rank tracking to check). Performance Max search categories are not included: they group searches and are not exact terms a rank check can look up. Money is in the account's currency (currencyCode); 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_terms_without_ranking"
  }
}

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

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses that nothing is bought or fetched, that positions come from saved rank checks, the 90-day cap, currency handling, and the cost model (no credits). It also explains the tracked/organicState semantics, which is real behavioral context. The one gap is that it doesn't clarify pagination or ordering ties beyond 'most spend first'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, which is good, but the middle is a dense run-on mixing column descriptions, field semantics, and caveats. Some content is redundant ('nothing is bought or fetched' restates 'Read-only; uses no credits'), costing readability.

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?

For a read-only analytical query with an output schema and full parameter coverage, the description covers the important decision points: what the rows mean, the tracked flag, the PMax exclusion, and the date/currency limits. The remaining details (row limits, defaults) live in the schema, which is appropriate.

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 coverage is 100%, so the schema already documents projectId, startDate, endDate, and limit fully. The description reinforces the 90-day window and date semantics but adds little parameter meaning beyond what the schema 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 precise resource and scope: paid search terms the site has no organic position for, sorted by spend, with cost/conversion and organic metrics. That is far more specific than the tool name alone. It never names a sibling such as get_google_ads_search_terms, so it stops short of explicit differentiation.

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 intent is implied well ('the spend organic work could replace') and caveats like Position Max exclusion are given, but there is no explicit when-to-use vs. when-to-use-another-tool statement. An agent must infer that this is the gap-analysis variant of the general search-terms tool.

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