Skip to main content
Glama

Outil.io

Connect search console

connect_search_console
Idempotent

Brancher Google Search Console sur le site Outil courant (domaine vérifié requis), sans OAuth : le compte de service Outil vérifie le domaine (jeton META publié dans les pages), crée la propriété, envoie le sitemap et ajoute ownerEmail (compte Google du client) comme propriétaire. status=pending : relancer après une minute. Pour un site hors Outil : demander au propriétaire d’ajouter l’email du compte de service (serviceAccount) comme utilisateur « Restreint » dans Search Console.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_search_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerEmailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare mutation/open-world/idempotent; the description adds the substance: no OAuth flow, domain verification via a published META token, property creation, sitemap submission, and granting ownerEmail owner rights. It also discloses asynchronous state (status=pending → retry) and the out-of-scope failure mode, which is exactly the behavior an agent needs before invoking a side-effecting tool.

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?

Front-loaded with the action and the key constraint (verified domain required, no OAuth), followed by the branching cases in order of likelihood. Dense but every clause carries operational information; only the parenthetical explanation of the META token is slightly extraneous for an agent deciding whether to call.

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 one-parameter, open-world mutating tool with no output schema, the description covers preconditions, side effects, async retry behavior, and the fallback when the precondition fails — nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (the single ownerEmail param is documented only as email/maxLength 191), and the description compensates by explaining that ownerEmail is the client's Google account and will be added as property owner. It also clarifies that serviceAccount is an internal value the owner must add manually, preventing confusion about a non-parameter.

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?

States a specific verb and resource — connect Google Search Console to the current 'Outil' site — and immediately scopes the mechanism (service account, no OAuth). This is unmistakably a provisioning/connection action, distinct from the read-only get_search_console_performance sibling.

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?

Gives usable conditions: a verified domain is required, and if status=pending the agent should retry after a minute, with an explicit manual fallback for sites hosted outside Outil (ask the owner to add the service-account email as a Restricted user). It stops short of naming sibling tools to use instead, but the preconditions and fallback path are concrete.

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.