Skip to main content
Glama

Rank Checker by GSC Wizard

List Search Console properties

list_sites
Read-only

Use this when the user asks which Search Console properties they can analyze. Lists all Google Search Console properties connected to the authenticated GSC Wizard account: the site URL (a domain property prefixed with sc-domain: or a URL prefix property), tags, and which data source backs the property. Properties another user has shared with you are included too, badged with sharedBy (the owner) and accessLevel (READ_ONLY or FULL). Each property row carries permissionLevel, readable and activated; a table view shows the last two as its Status column ("Not verified in GSC" for readable: false, "Not activated" for activated: false, empty when both are true). permissionLevel is the Google Search Console permission (siteOwner / siteFullUser / siteRestrictedUser / siteUnverifiedUser), and readable: false means Google will refuse every data request for that property: it is listed in Search Console but not verified, so the user must verify it at search.google.com/search-console before any report will work, and other tools refuse it with reason property_not_verified. Do not attempt reads on a property with readable: false; tell the user to verify it instead. Activating it does not help. activated: false means the property is connected but is not shown on the account dashboard and is not synced to full storage, or is shown but past the plan's dashboard property limit, so every other property-scoped tool will refuse it (reason property_not_selected or over_api_property_limit). Do not attempt reads on those either: where this connection offers it, call set_dashboard_visibility to activate the property first (hiding another one if the plan is at its limit), or choose one with activated: true. Properties shared with the caller are always activated: true, because the grant is itself the selection; a share whose owner no longer has an active GSC Wizard plan is left out, since no tool can read it. gscScope is the Search Console access of the Google connection behind the property: "full" allows submit_sitemap and create_gsc_property, "readonly" means Google will refuse those two (reads still work); absent when unknown. Not for Bing, Yandex or GA4: use list_bing_sites, list_yandex_sites or list_ga4_properties. Owned properties come first, then shared ones, each by siteUrl ascending.

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": "list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
newNo
hintNo
kindNoWidget variant: "kpis", "table", or "sections".
kpisNoKPI cards (kind="kpis").
lostNo
noteNoCaveat about the result, when the tool returned one.
rowsNoData rows (kind="table"), each with every field of the tool's own row; columns name the ones drawn.
notesNoCaveats about the result, when the tool returned several.
rangeNoThe window the numbers cover.
scopeNoThe brand, content group or topic cluster filter these numbers are narrowed to; absent when the call was unscoped and the numbers cover the whole property.
titleNo
blocksNoStacked sub-blocks (kind="sections").
countsNoget_ranking_changes: the full size of each bucket before `limit`.
deltasNoget_site_summary: current minus previous (ctrPoints in percentage points).
reasonNo
sourceNo
thenByNoSecondary sort field, when the tool states one.
accountNo
columnsNoColumn defs (kind="table").
currentNoget_site_summary: the window's totals (ctr 0-100, impression-weighted avgPosition).
summaryNoMetric totals keyed by GA4 metric name.
warningNoA caveat that changes how the numbers read.
coverageNoHow much of the property total the returned rows cover, with the property totals inline. Quote totals from here; do not sum the rows.
declinedNo
improvedNo
nextStepNo
orderingNoSort order per list, when the result holds several lists.
previousNoget_site_summary: the comparison window's totals.
sortedByNoRow field the rows are sorted by.
timeZoneNoGA4 property's IANA reporting time zone.
dailyRowsNoget_site_summary: the window day by day, oldest first.
dimensionNo
emptyTextNo
scanLimitNo
siteScopeNoSet when GA4 numbers were narrowed to this site's hostnames because the property is shared with other sites.
sortOrderNo"asc" or "desc".
thenOrderNoThe tie-break's direction, present only when it differs from sortOrder.
totalRowsNo
assistantsNoget_ga4_llm_traffic: one row per AI assistant (the table rows).
comparisonNoThe comparison window (get_site_summary, get_ranking_changes).
dataSourceNoWhere the numbers were read from: the warehouse or the live API.
hasRevenueNo
paginationNoWhere this page of rows sits in the whole result, and how to fetch the next one.
timeseriesNoget_ga4_overview with includeTimeseries: daily points, oldest first.
partialDaysNoRequested days after settledThrough; their numbers are still incomplete.
prevSummaryNoThe comparison period's totals; null when it has no GA4 data.
currencyCodeNo
dataMaturityNo
emptyBecauseNo
ga4OnlyCountNo
gscOnlyCountNo
hasEcommerceNo
landingPagesNoget_ga4_llm_traffic: landing pages of AI assistant sessions.
matchedCountNo
methodLimitsNo
hasComparisonNo
notConfiguredNo
totalSessionsNo
prevTimeseriesNoThe comparison period's daily points; null when it has no GA4 data.
reauthRequiredNo
settledThroughNoLast day the data is complete through.
comparisonRangeNoThe comparison window of a GA4 view tool; null when there is none.
ecommerceSummaryNo
sourceTimeseriesNoget_ga4_llm_traffic with includeDailySplit: daily sessions per assistant.
comparisonHasDataNofalse when the comparison period has no data at all, so there is no comparison.
matchedClickShareNoA 0-1 fraction of the named-query clicks the estimates cover.
prevTotalSessionsNo
previousDailyRowsNoget_site_summary: the comparison window day by day, oldest first; absent for a window over 180 days.
llmShareOfSessionsNoA 0-1 fraction.
coverageUnavailableNoWhy coverage is null, when it is.
warehouseLatestDateNoNewest day the warehouse holds for the property; days after it in the range are missing, not zero.
prevEcommerceSummaryNo
prevLlmShareOfSessionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description goes well beyond that by explaining shared-property inclusion, gscScope effects on submit_sitemap/create_gsc_property, and the downstream refusal reasons (property_not_verified, property_not_selected, over_api_property_limit). The only minor gap is that it does not discuss result size or pagination for the listing itself.

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 first sentence is well front-loaded and the ordering rule is a useful closer, but the middle is a dense, repetitive block: the 'do not attempt reads' warning is restated for both readable:false and activated:false, and several output-field meanings are re-explained despite an existing output schema. It is informative but longer than needed for a zero-parameter listing tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a zero-parameter tool with an output schema and read-only annotations, the definition covers the remaining risk areas thoroughly: which properties appear, why some are excluded, what each status field implies, and what the agent should do instead of reading an unusable property. Nothing needed to call or interpret this tool is missing.

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

Parameters4/5

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

There are zero input parameters, so the baseline is 4. The description does not need to define inputs, and instead spends its space on output field semantics, which the parameter dimension does not penalize.

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?

The description opens with a concrete trigger ('when the user asks which Search Console properties they can analyze') and states exactly what is listed: site URL, tags, data source, plus shared properties. It explicitly names the non-overlapping siblings (list_bing_sites, list_yandex_sites, list_ga4_properties), so an agent can separate this from other list tools without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use condition, then multiple when-not-to cases: do not read properties with readable:false or activated:false, and use set_dashboard_visibility to activate instead. It also routes to the correct sibling for non-GSC platforms, which is unusually complete routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.