Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Link to connect Search Console

integrations_gsc_connect_link
Read-onlyIdempotent

A link the person opens to connect Google Search Console for the site (Google needs a human click). Give the person the link; afterwards integrations_status shows the connection.

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_gsc_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent read operation, so the bar is lower, but the description adds the critical behavioral fact: the connection requires a human click and cannot complete server-side. It also names the verification path afterward. It omits details like link expiry, single-use behavior, and whether re-calling mints a new link, which keeps it from a 5.

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?

Two short sentences, front-loaded with what the tool returns and why a human is required. 'Give the person the link' restates the opening clause slightly, so there is minor redundancy, but no wasted structure.

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 simple one-parameter tool with no output schema, the description explains the human-click workflow and the verification step well. It leaves the caller unsure about the exact siteId format and the return shape (presumably a URL string), which are the two remaining things an agent needs to invoke it correctly.

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?

There is one required parameter, siteId, with 0% schema description coverage, so the description must carry the meaning. The phrase 'for the site' only hints that siteId identifies the site, without saying whether it is a Search Console property string, a URL, or an internal site identifier. This is a meaningful gap for the only input the agent must supply.

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 clearly states that this returns a link a human opens to connect Google Search Console, which is a specific effect rather than a tautology. It also distinguishes itself from integrations_status by naming the follow-up check. It stops short of a crisp 'generates/returns' verb, but an agent can tell what the tool produces.

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 gives clear operational guidance: give the link to the person, and note that Google requires a human click, so the agent knows this is not a programmatic connect call. It also routes the agent to integrations_status afterwards to verify the connection. It does not mention whether other search-console tools apply before connecting, so a 4 rather than 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