Webanto

List keyword topics

webanto_list_keyword_topics

Read-onlyIdempotent

List the topics from the organization's newest completed keyword grouping: each topic's label, search intent, summed clicks and impressions, impression-weighted position, its biggest queries, and the pages earning its impressions. page_focus is owned (one page carries it), competing (a second page holds 30% or more, so two pages split the same searches) or scattered (no page holds 60%); null when the topic has under 30 impressions. Metrics are read live from the imported Search Console window the grouping covered. Grouping itself is started from the dashboard; this tool only reads. run is null until a grouping has completed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webanto_list_keyword_topics"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	next_cursor from the previous page. Omit for the first page.
`page_size`	No	Topics returned per page, biggest by impressions first.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real behavioral context beyond them: metrics are read live from the imported Search Console window the grouping covered, page_focus is null below 30 impressions, and run is null until completion. It does not mention pagination limits, which the schema supplies instead.

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-loads the resource and its returned fields, then defines the page_focus vocabulary and the data provenance. Every sentence carries information, though the 'this tool only reads' clause partly restates readOnlyHint, and the dense enumeration of returned metrics sits close to what the output schema already declares.

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 two-parameter read tool with an output schema, the definition covers preconditions, null semantics, enum-like page_focus values and data freshness. The return-field enumeration is somewhat redundant with the existing output schema, but nothing needed to call it correctly is missing.

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%, so cursor and page_size are already fully documented, including ordering 'biggest by impressions first'. The description adds no syntax or formatting detail for these parameters, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource with scope: 'List the topics from the organization's newest completed keyword grouping', and enumerates what each topic carries. This clearly separates it from siblings such as list_keywords and list_tracked_keywords, which operate on keyword lists rather than grouped topics.

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 clear usage context: the grouping must have been started from the dashboard, this tool only reads, and 'run is null until a grouping has completed' defines the precondition for meaningful results. It stops short of explicitly naming an alternative sibling to use when no grouping exists, so it earns 4 rather than 5.

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

All Webanto tools Inspect

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

Need Help?