Skip to main content
Glama

ai_get_top_queries

Retrieve the top grounding queries from imported AI Search Queries reports to identify which search queries drive AI citations for a site.

Instructions

Get top grounding queries from imported AI Search Queries reports.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "ai_get_top_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of queries to return (default 20)
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it is thin. It never explains what makes a query "top" (volume? citations? grounding frequency?), the sort order, or whether results are bounded by the siteUrl scope - all material to interpreting the output of a read-only analytics call.

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?

A single efficient sentence with the resource and source front-loaded and no filler. It is arguably too terse for what it needs to convey, but nothing is wasted.

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

Completeness3/5

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

For a simple two-parameter read tool with a fully documented schema and no output schema, this is close to adequate. The unresolved ambiguity around ranking criteria and the import prerequisite keeps it from being complete.

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 limit default of 20, so the schema does the heavy lifting. The description adds only the implicit link between siteUrl and the imported report scope, with no further parameter semantics.

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 specific verb+resource ("Get top grounding queries") and a specific data source ("imported AI Search Queries reports"), which distinguishes it from siblings like ai_get_top_cited_pages or ai_get_top_intents. It stops short of naming those siblings, so the differentiation is inferred rather than explicit.

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 phrase "from imported ... reports" implies a prerequisite (a report must have been imported first), which is useful context. However, there is no explicit guidance on when to choose this over the other ai_get_top_* tools or what to do if no import exists.

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