Skip to main content
Glama

ai_get_top_intents

Retrieves and ranks the top search intents from AI Search Queries reports for a site, helping you identify which user intents drive AI citations.

Instructions

Get top intents aggregated from 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_intents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of intents to return (default 10)
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden of disclosure; it only weakly implies a read via "Get". It says nothing about the aggregation window, ranking basis for "top", whether results are sampled or complete, or what the response contains, which matters for a reporting tool with no output schema.

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 short sentence with no filler and the resource front-loaded. Its brevity is appropriate, though it borders on under-specification rather than being tightly informative.

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 two-parameter read-only reporting call with no output schema, the description covers the bare essentials of what is retrieved. It is still missing the definition of an "intent" and any sense of the returned structure, which an agent needs to interpret results correctly.

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%, and both parameters (siteUrl, limit with its default of 10) are documented in the schema itself. The description adds no meaning beyond that — no explanation of what counts as a site URL scope or how limit interacts with aggregation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and object ("Get top intents") and a data source ("AI Search Queries reports"), which is more than a restatement of the name. However, it never clarifies how an "intent" differs from the sibling resources "queries" or "topics" (ai_get_top_queries, ai_get_top_topics), so an agent cannot confidently choose between them from the text alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implied usage comes from the phrase "aggregated from AI Search Queries reports", which an agent must interpret as a prerequisite rather than being told it explicitly.

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