Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

searchconsole.sites.get

Fetches details for a specific Search Console site by URL, enabling property inspection and verification.

Instructions

Retrieves information about specific site [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, list.

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.
siteUrlYes[URL path segment] The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault
siteUrlNo
permissionLevelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / siteUrl / description
      Previous value: -"The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`."New value: +"[URL path segment] The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "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"
+}
  2. First observed

TDQS

B3.1/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 behavioral burden. It discloses that this is an HTTP GET returning JSON, but it does not mention required Search Console permissions, error behavior, or why body-building options apply to a GET; the body/body_file language is generic boilerplate rather than useful behavior for this endpoint.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, and the sibling note is useful. The second sentence is long and includes generic request-body mechanics that are not clearly relevant to a GET site lookup, adding clutter without much value.

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?

Because schema coverage is complete and an output schema exists, the description need not explain parameter details or return shape. It is adequate for identifying the operation, but for a tool with no annotations it omits relevant behavioral context such as permission requirements.

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%, so the input schema already documents all five parameters, including siteUrl examples and the roles of params, query, dry_run, and body_file. The description only restates the typed-parameter precedence and body_file behavior, adding little beyond the schema.

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?

The description states a specific verb and resource: it retrieves information about a specific Search Console site. It also distinguishes the tool from its same-resource siblings by naming add, delete, and list, though it does not say exactly what site information is returned.

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?

It lists the sibling operations over the same resource, which implies this tool is for retrieving one site rather than adding, deleting, or listing sites. However, it does not explicitly state when to choose get versus list or mention any prerequisites.

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