Skip to main content
Glama

search_console_sites_get

Fetch metadata and permission level for a Search Console property to verify write access before submitting sitemaps.

Instructions

Fetch metadata and the current user's permission level for a single Search Console property. Returns the raw Webmasters API response shape: {siteUrl, permissionLevel ('siteOwner'|'siteFullUser'|'siteRestrictedUser'|'siteUnverifiedUser')}. Read-only; no mutation. Use this to verify whether the authenticated account has write access before calling mutating tools like search_console_sitemaps_submit. For a full list of accessible properties use search_console_sites_list; for per-URL indexing data use search_console_url_inspection_inspect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesProperty identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com'). The property must be verified and accessible to the authenticated Google account.
Behavior5/5

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

Declares read-only and no mutation. Specifies exact return shape with permission level enum values. Even mentions the property must be verified/accessible. No annotations provided, so description covers it fully.

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

Conciseness5/5

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

Three concise sentences, front-loaded with action, no fluff. Each sentence serves a purpose: action, return shape, and usage guidance.

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?

For a single-parameter, no-output-schema tool, the description fully specifies return shape, permission levels, read-only nature, and sibling connections. No gaps.

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?

Input schema already has 100% coverage with detailed description of site_url format. The main description does not add further parameter details beyond context, so baseline 3 is appropriate.

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?

Clearly states it fetches metadata and permission level for a single Search Console property. Distinguishes from siblings by naming alternatives like search_console_sites_list and search_console_url_inspection_inspect.

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?

Explicitly says when to use: to verify write access before mutating tools. Also points to siblings for other use cases, providing clear context and exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server