get_all_page_statusesGet Google Search Console indexing status for all pages in a project, as last synced from Google
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | The project ID |
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | Why there are no statuses, in place of the list | |
| warning | No | Set when the connected Search Console property does not cover the address the site is served at | |
| statuses | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "message": {
+ "description": "Why there are no statuses, in place of the list",
+ "type": "string"
+ },
+ "statuses": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "coverageState": {
+ "type": "string"
+ },
+ "cwvCategory": {
+ "type": "string"
+ },
+ "indexingState": {
+ "type": "string"
+ },
+ "lastCrawlTime": {
+ "type": "string"
+ },
+ "pageId": {
+ "type": "string"
+ },
+ "performanceScore": {
+ "type": "number"
+ },
+ "url": {
+ "type": "string"
+ },
+ "verdict": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "warning": {
+ "description": "Set when the connected Search Console property does not cover the address the site is served at",
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a genuinely useful trait beyond the schema: the data is 'as last synced from Google', disclosing that results are a cached snapshot rather than a live query — material for an agent deciding whether to re-check. It omits any prerequisite that a GSC connection must exist, which caps it below 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence with zero waste, front-loaded with the verb and resource, and the scope qualifier follows immediately. Nothing is padded or repeated from the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the single required parameter is fully documented in the schema. For a simple read-only batch-status tool, the only substantive extra an agent needs — that the data is a sync snapshot — is already stated; the missing GSC-connection prerequisite is minor.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single projectId parameter, so the schema already carries the semantics. The phrase 'in a project' confirms the scoping but adds nothing beyond what the schema states; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (get Google Search Console indexing status for all pages in a project), and the plural 'all pages' implicitly separates it from the singular get_page_index_status sibling. It does not explicitly name that sibling, so the differentiation is inferable rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling get_page_index_status for per-page lookups or inspect_url for live inspection. The usage is implied by the scope phrase 'for all pages in a project', which is enough to act on but leaves the agent to infer alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.