Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Integrations

integrations_status
Read-onlyIdempotent

Whether Google Search Console is connected for the site, the Google accounts and properties it can use, and the selected property. integrations_gsc_connect_link connects it, and seo.set_search_console_site chooses the property.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavioral context: this tool reports the accounts/properties available and which property is currently selected, and it delegates connection and selection to other tools. It stops short of saying how a disconnected state is surfaced (error vs. status payload), which is the main remaining gap.

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

Conciseness4/5

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

A single dense sentence that front-loads what is returned and appends the sibling routing at the end, with no filler. It is slightly run-on, packing three reported facts plus two sibling references into one sentence, which costs a bit of scanability.

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

Completeness3/5

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

For a one-parameter read-only status tool with no output schema and full annotation coverage, the description conveys what information comes back and where mutations live. However, it leaves the caller unsure about the disconnected case and about the siteId format, which matter for correctly interpreting a status response.

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?

The single parameter siteId has 0% schema description coverage, so the description must carry the burden. The phrase 'for the site' weakly implies the parameter scopes the lookup to a site, but it never names siteId, its expected format (ID vs. domain), or what happens if it is omitted. This is a partial compensation, not full.

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 the specific resource (Google Search Console connection state for a site) and enumerates what it reports: connection status, usable Google accounts/properties, and the selected property. It also explicitly distinguishes itself from integrations_gsc_connect_link and seo.set_search_console_site, so an agent can tell it is the read/status counterpart. The only shortfall is that the verb is implicit ("Whether ... is connected") rather than an explicit action 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?

By naming integrations_gsc_connect_link for connecting and seo.set_search_console_site for selecting the property, it tells the agent when to use this tool (inspection) versus those siblings (mutation). It does not state an explicit exclusion such as 'do not use to connect' or any prerequisite, which keeps it below a 5.

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