Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get the DNS record to verify the site

google_verification_record
Read-onlyIdempotent

The DNS TXT record that proves the person owns the site's domain, for Google Search Console, with where to add it (the domain's DNS host and a link when Sextant knows it). After the person adds it, run google.verify_site.

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": {
      "siteId": "<siteId>"
    },
    "name": "google_verification_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes
gscAccountIdNoThe Google account to verify with (from google.setup_status). Default: the first one that allows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the returned record includes where to add it (DNS host and a link when known), which is return-shape information no output schema provides. It says nothing about whether the record is stable across calls or what happens on failure.

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?

Two sentences with zero filler; the resource definition is front-loaded and the follow-up action comes second in the order it is needed.

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

Completeness4/5

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

Given no output schema, the description usefully characterizes what comes back (a TXT record plus its placement location). What remains uncovered is the siteId parameter's meaning, which is the one required input and is undocumented everywhere.

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?

Schema description coverage is only 50%: gscAccountId is documented in the schema with its default, but siteId is undocumented in both schema and description. The description never mentions any parameter, so an agent gets no help resolving which site the record is for or how the account affects the returned record.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — the DNS TXT record proving domain ownership for Google Search Console — which no sibling tool covers. The verb is implicit (supplied only by the title 'Get the DNS record'), so it falls just short of a self-contained verb+resource statement.

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

Usage Guidelines4/5

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

It clearly frames the workflow: fetch this record, have the person add it, then run google.verify_site. That sequencing is concrete guidance, but there is no exclusion guidance (e.g., when to check google_setup_status first or what to do if verification is already pending).

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.

Resources