search_get_top_queriesTop Search Console queries for this account.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| days | No | ||
| limit | No | ||
| action | No | ||
| status | No | ||
| date_to | No | ||
| page_id | No | ||
| sort_by | No | ||
| user_id | No | ||
| site_url | No | ||
| client_id | No | ||
| date_from | No | ||
| ad_account | No | ||
| ig_user_id | No | ||
| user_email | No | ||
| range_preset | No | ||
| activity_only | No | ||
| campaign_name | No | ||
| property_name | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / actionAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Action"
+}Input schema / properties / statusAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Status"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured metadata. The description adds no behavioral context beyond the purpose statement: it does not clarify account scoping, permissions, pagination, or how the top queries are selected or ranked.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasteful wording. However, it is too terse for a tool exposing 19 optional parameters, so its conciseness comes at the cost of missing essential context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists and return values need not be explained, the description is grossly incomplete for a tool with 19 optional parameters spanning dates, limits, account identifiers, campaign/property names, and filters. An agent would have to infer nearly all invocation semantics from bare parameter titles.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are 19 input parameters with 0% schema description coverage, and the description mentions none of them. Parameters such as action, status, page_id, ad_account, ig_user_id, campaign_name, property_name, range_preset, and activity_only are completely unexplained, leaving the agent unable to interpret their meaning or expected values.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific Search Console resource, 'Top Search Console queries,' and scopes it to 'this account.' It is clear enough for an agent to identify the general purpose, but it does not distinguish this tool from the many sibling search_* tools or explicitly state that it returns a ranked list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives such as search_get_metrics, search_get_keyword_gap, or other search_* tools. It also omits prerequisites, exclusions, and any indication of what kind of account or property is expected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.