Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search Console: List properties

google_search_console_list_properties
Read-only

List all Search Console properties available to an authenticated user, including property URLs and permission levels, to help identify accessible sites and their access rights.

Instructions

[UNIFIED] List all Search Console properties (sites) the authenticated user has access to, with their permission levels. Returns property URLs (domain properties as sc-domain:example.com, URL-prefix properties as https://example.com/) and permission levels (siteFullUser, siteOwner, siteRestrictedUser).

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": {
      "site": "<site>"
    },
    "name": "google_search_console_list_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds genuinely useful behavioral context beyond it: the two property-URL formats (sc-domain: vs https://), the three permission-level values, and the implicit auth requirement of the authenticated user. It does not mention pagination or empty-result behavior, which keeps it from a 5.

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?

Two dense, front-loaded sentences with no filler; purpose comes first, return format second. The only waste is the "[UNIFIED]" tag, which conveys nothing actionable to an agent.

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?

With no output schema, the description does some of the return-value work by naming URL formats and permission levels. However, the unexplained required `site` parameter and absent pagination/completeness notes leave an agent guessing at invocation for a simple one-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter (`site`) with 0% schema description coverage, and the description never mentions it at all — notable because a required `site` argument on a 'list all properties' call is counterintuitive and needs explanation. The return-value detail is good, but parameter meaning is entirely unaddressed.

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 ("List all Search Console properties (sites)") plus the exact scope ("the authenticated user has access to"). It also enumerates the two return shapes (domain vs URL-prefix) and permission levels, so an agent can distinguish it from list_sitemaps or inspect_url without opening the schema.

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?

Usage is only implied: the phrase "the authenticated user has access to" signals this is a discovery/enumeration call, but there is no explicit when-to-use, no prerequisite statement, and no named alternative among the Search Console siblings. Adequate but leaves routing to inference.

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