list_gsc_properties

Cost: Free (0 credits).

list_gsc_properties shows every Search Console property on the Google accounts you have connected — each one's permission level, whether SeoGrep can read its performance data, and which project reads it. It is the tool to reach for when a property you can see in Search Console does not seem to be available here.

What it does

For each connected Google account it asks Google for that account's property list, then lines each property up against your projects. A property your account cannot query is still listed, marked NOT QUERYABLE with its permission level, so a property is never silently missing. Nothing is cached: the list is read live, every time.

It names the project a property plainly belongs to

A property no project reads is not left as a bare "not used by any project". If one of your projects names the same site and reads no property yet, the line names that project and tells you to run track_gsc_property to link them. Both sides used to be printed with nothing to say they belonged together, which left one free call undone for as long as nobody noticed.

The match ignores a leading www. on either side and nothing else. A subdomain is a different site and is never offered: blog.example.com is not example.com. And only a project that reads no property qualifies — a project already bound to a different property is in a deliberate state, and offering to link it would really be offering to repoint it.

A project that still holds a property but lost the Google account behind it is named on that property's line too, with connect_gsc as the repair. Disconnecting an account leaves the mapping in place and clears the account, and such a project used to appear in neither hint — it was printed as "not used by any project" while list_projects said of the very same project that it was still mapped. It is not offered track_gsc_property: the mapping is already there, and it is the account that has to come back.

The order is fixed

For one account, the properties are always listed in the same order, so two reads of the same inventory line up against each other. Google's own listing carries no ordering promise, and printing it as it arrived returned the same 27 properties in two different orders on two calls a second apart.

When an account cannot be read

If Google refuses — an expired connection, an outage — that account is reported as could not be read, never as an account with no properties. An absence we did not observe is not an absence, and the difference is what tells you to reconnect rather than to go and verify a property that was there all along. The other accounts are still listed.

Example

Ask your MCP client in plain language:

Which Search Console properties can SeoGrep see?

Then map one to a project on the Connection page, or with connect_gsc if the account is not connected yet.

Input

No parameters.

Returns

One block per connected Google account: its email and account_id, then one line per property with its permission level, the projects reading it through that account, and — where it applies — why SeoGrep cannot query it.