Flinty

Search Performance

get_metrics

Idempotent

Get Google Search Console metrics summary (clicks, impressions, top queries). May query Google live and refresh the stored OAuth connection state when required.

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

Input Schema

Name	Required	Description	Default
`query`	No	Filter top_queries to a specific search query (partial match) instead of the top 10 by clicks
`period`	No	Time period: '7d', '30d', or '90d' (default '30d')

Output Schema

Name	Required	Description	Default
`since`	No
`clicks`	No
`period`	No
`message`	No
`impressions`	No
`top_queries`	No
`avg_position`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the tool may query Google live and refresh stored OAuth connection state. That explains the readOnlyHint=false side effect and adds meaningful behavioral context. It stops short of describing how often the refresh occurs or what happens if OAuth refresh fails.

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?

The definition is two front-loaded sentences with no wasted wording. The primary purpose comes first, followed by the important live-query/OAuth-refresh caveat.

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 that the input schema is fully described, an output schema exists, and annotations cover safety and openness, the description is broadly complete. It could be slightly stronger by clarifying when to choose this over sibling analytics tools.

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 100%, so both parameters are already documented in the input schema. The description does not add parameter-specific meaning beyond what the schema provides, which establishes the baseline score.

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 states a specific verb and resource: getting a Google Search Console metrics summary with clicks, impressions, and top queries. This is clear and distinct from sibling tools like get_geo_analysis or get_top_pages, though it does not explicitly name those alternatives.

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

Usage Guidelines3/5

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

Usage is implied by the Google Search Console context, so an agent can infer it is for search performance metrics. However, the description gives no explicit when-to-use or when-not-to-use guidance versus related siblings such as get_top_pages.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Flinty tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?