Skip to main content
Glama

ai_get_top_topics

Retrieve top topics aggregated from AI Search Queries reports for a site, with an optional result limit, to identify which subjects AI citations emphasize.

Instructions

Get top topics 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_topics"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden; "Get" suggests retrieval and "aggregated" explains the derivation, but read-only behavior and report dependencies are not established. Ranking criteria, time window, freshness, and result behavior also remain unspecified.

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

Conciseness5/5

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

The single sentence is front-loaded and waste-free, with the aggregation source adding useful information in very few words. Its sparse operational detail is a completeness issue rather than a structural or verbosity problem.

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 retrieval tool, the description and complete input schema are sufficient for a basic invocation. With no output schema or annotations, however, the missing ranking and time-scope behavior and lack of sibling differentiation leave notable gaps for reliable selection and interpretation.

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?

The schema fully describes both siteUrl and limit, including limit's default of 10, so the high-coverage baseline applies. The description adds no parameter meaning beyond the schema, such as accepted site URL forms or how the limit applies to aggregated topics.

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?

"Get top topics" states a specific retrieval action and resource, while "aggregated from AI Search Queries reports" identifies the data source and derived nature of the results. It does not explicitly distinguish topics from the sibling query- and intent-focused rankings.

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 wording implies use when an agent wants an aggregated topic ranking based on AI Search Queries reports. It provides no explicit when-not guidance, prerequisites, or pointer to alternatives such as ai_get_top_queries or ai_get_top_intents for different views.

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