Skip to main content
Glama
Sign In

Maqui Analytics

by io.github.luis-fuentes
OverviewDiscussionsAdmin

Términos de búsqueda de Google Ads

list_google_ads_search_terms
Read-only

[DEMO SINTÉTICA] Búsquedas reales que escribieron los usuarios y dispararon nuestros anuncios de Google Ads. Muestra términos exactos con clics y gasto. Cubre siempre los últimos 30 días a la fecha de la última sincronización; no admite otro período. Útil para encontrar oportunidades (nuevas keywords) o exclusiones (queries irrelevantes). Sirve para "qué buscan los usuarios", "términos de búsqueda", "search terms".

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesHasta 100 filas ordenadas por gasto, agregadas en los últimos 30 días a la fecha de la última sincronización; una consulta puede aparecer en varias campañas.
demoNoSolo aparece en demo; todos sus datos son ficticios.
noticeNoAviso obligatorio de datos sintéticos cuando demo es true.
sample_periodNoPeríodo fijo de los ejemplos sintéticos; no cambia al solicitar otro rango.
requested_periodNoRango solicitado a la demo; no es el período real de sus ejemplos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / date_range
      Removed value: -{
-  "description": "Período a consultar. Ejemplos: \"últimos 30 días\", \"enero 2025\", \"2025-01-01 a 2025-01-31\", \"este mes\", \"mes pasado\". Por defecto: últimos 30 días.",
-  "type": "string"
-}
    • changedOutput schema / properties / data / description
      Previous value: -"Hasta 100 filas ordenadas por gasto; una consulta puede aparecer en varios días o campañas."New value: +"Hasta 100 filas ordenadas por gasto, agregadas en los últimos 30 días a la fecha de la última sincronización; una consulta puede aparecer en varias campañas."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the fixed rolling 30-day window anchored to the last sync, and that no custom date range is possible — a constraint an agent would otherwise guess wrong on.

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?

Front-loaded with what the data is, then the hard time-window constraint, then usage. The trailing quoted phrase list ('qué buscan los usuarios', 'términos de búsqueda', 'search terms') is retrieval filler but harmless and short.

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?

With zero parameters, annotations covering safety, and an output schema handling return values, the description supplies what is missing: fixed time window, what metrics come back, and why you'd call it. Only the absence of explicit sibling routing keeps it below 5.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. Nothing in the description contradicts or obscures the empty schema.

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?

States a concrete resource with scope: real user queries that triggered Google Ads, showing exact terms with clicks and spend. That distinguishes it conceptually from list_google_ads_keywords (which returns the keywords you bid on, not the queries), though it never names the sibling outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit use cases (finding new keyword opportunities, building negative-keyword exclusions) and a hard constraint: only the last 30 days up to the last sync date, no other period supported. Missing an explicit 'for X instead use list_google_ads_keywords' routing statement, which keeps it from a 5.

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

All Maqui Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources