Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

searchconsole.sites.list

Lists the authenticated user's Search Console sites, helping you confirm which properties are available before adding, deleting, or retrieving site details.

Instructions

Lists the user's Search Console sites [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: add, delete, get.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault
siteEntryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "siteEntry": {
+      "items": {
+        "properties": {
+          "permissionLevel": {
+            "enum": [
+              "SITE_PERMISSION_LEVEL_UNSPECIFIED",
+              "SITE_OWNER",
+              "SITE_FULL_USER",
+              "SITE_RESTRICTED_USER",
+              "SITE_UNVERIFIED_USER"
+            ],
+            "type": "string"
+          },
+          "siteUrl": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description discloses that this is an HTTP GET operation and returns JSON, which establishes read-only behavior and response format. It does not mention authentication requirements, rate limits, or pagination behavior, so it carries only part of the behavioral burden.

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?

The purpose and sibling alternatives are front-loaded and useful. The generic explanation of request-body construction is somewhat boilerplate for a list operation, but the description remains relatively efficient.

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 simple list tool with full schema coverage and an output schema, the description covers purpose, HTTP method, response format, and sibling alternatives. Authentication details are omitted, but the essential information for selecting and invoking the tool is present.

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 the schema already documents all four parameters. The description adds a note about typed parameters winning over the params map, but that is already reflected in schema descriptions and does not add much new meaning.

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: 'Lists the user's Search Console sites.' It also explicitly distinguishes the tool from sibling operations on the same resource by naming add, delete, and get.

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?

The description names the sibling operations over the same resource, which gives clear context for when this list operation is appropriate versus add/delete/get. It does not state explicit exclusions or conditions, but the usage is clear.

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

Deploy Server

Other Tools