Skip to main content
Glama

SEO Rank Fixer

Site performance

site_performance
Read-onlyIdempotent

Google Search clicks, impressions, CTR and average position for one site over a date range, compared with the period before.

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

Input Schema

NameRequiredDescriptionDefault
rangeNoDate range, default 28d. Some plans include only the last 28 days.
siteIdYesA site id from list_sites.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds a genuinely non-obvious behavioral trait: results are automatically compared against the preceding equivalent period, something not expressible through any parameter. It stops short of saying how that comparison is returned.

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?

A single front-loaded sentence listing metrics first, then scope, then range, then the comparison twist. No filler, no redundancy with the title.

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?

For a two-parameter read-only analytics tool with full schema coverage, no output schema, and complete annotations, the description supplies what an agent needs to select and call it. The one residual gap is that the automatic period comparison is stated but not explained in terms of output shape.

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%, including the enum and plan-related limitation on range, so the schema does the parameter work. The description only restates 'date range' and 'one site' without adding format, default, or interaction detail beyond the schema.

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?

Names the exact metrics returned (clicks, impressions, CTR, average position), the scope (one site), and the range, all with a concrete verb-less but unambiguous resource statement. It does not, however, distinguish itself from likely-adjacent siblings such as search_report or rank_tracking, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only implicit signal is the 'one site' scoping, which the schema's siteId description already supplies via 'A site id from list_sites.'

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.