Skip to main content
Glama

Outil.io

Get search console performance

get_search_console_performance
Read-only

Google Search Console via le compte de service Outil (aucune connexion OAuth) : propriété correspondant à siteUrl, clics, impressions, CTR et position moyenne sur la période, top requêtes, top pages, et requêtes à potentiel (positions 4–20 avec impressions mais peu de clics) à travailler en priorité.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "get_search_console_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
siteUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds the auth mechanism (service account, no OAuth) and, since there is no output schema, names which metrics come back, which is genuinely useful. It says nothing about Search Console row limits, sampling, quota/rate limits, or lag in data freshness, which are real behavioral traits for this API.

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

Conciseness3/5

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

It is a single dense sentence, front-loaded with the source system and auth caveat, and every clause carries information. It is somewhat run-on, with the return-value list stacked after a colon, but no filler. Structure is acceptable, though a break between auth context and returned data would read better.

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?

With only two parameters and no output schema, the description covers the important omissions: what the tool returns and how it authenticates. The one real gap is the period parameter, whose default and range are never explained in prose. Otherwise an agent has enough to call this correctly.

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?

Schema description coverage is 0%, so the description must carry the burden. It clarifies that siteUrl identifies the Search Console property, which is a meaningful addition beyond 'string/uri'. The days parameter is only referenced obliquely as 'sur la période'; the default of 28 and the 7–480 bounds are left to the schema without explanation.

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 verb-resource pair (retrieve Google Search Console performance for the property matching siteUrl) and enumerates the delivered artifacts: clicks, impressions, CTR, average position, top queries, top pages, and opportunity queries. The parenthetical about the service account implicitly separates it from the connect_search_console sibling, which handles OAuth. It stops short of an explicit sibling contrast, which keeps it at 4.

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?

'via le compte de service Outil (aucune connexion OAuth)' tells the agent this works without first running the OAuth connection sibling. It also states the 'requêtes à potentiel (positions 4–20...)' are data to 'travailler en priorité', hinting at the follow-up use case. No explicit when-not-use condition is given.

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.