Skip to main content
Glama

SEO Rank Fixer

Search report

search_report
Read-onlyIdempotent

Top queries, pages, countries or devices for one site, with clicks, impressions, CTR and position against the previous period. Use filter to find winners or losers.

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>",
      "dimension": "<dimension>"
    },
    "name": "search_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
rangeNoDate range, default 28d. Some plans include only the last 28 days.
filterNo
searchNoOnly rows containing this text.
siteIdYesA site id from list_sites.
dimensionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are comparative against the previous period, and the dimensions are enumerated. It omits pagination/limit defaults, result-size caps, and plan-based range restrictions.

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?

Two tight sentences, front-loaded with what is returned and the metric set, followed by the one usage hint. No filler, no restatement of 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?

With no output schema, the description usefully enumerates the returned columns (clicks, impressions, CTR, position) and the comparison behavior, which is the main thing an agent needs to interpret results. Minor gaps remain around sort semantics and row limits for a 7-parameter tool, but nothing critical is missing.

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 coverage is 43%, so the description must compensate and only partly does: it explains dimension values (query/page/country/device) and implies filter semantics (winning/losing). The sort options, notably clicksChange, and the limit cap of 100 are left entirely to the schema with no interpretive help.

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 concrete resource being returned (top queries/pages/countries/devices for one site) and the metrics included (clicks, impressions, CTR, position) with a comparison baseline (previous period). That is enough to distinguish it from siblings like site_performance or opportunities, though the description never explicitly names an alternative.

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?

'Use filter to find winners or losers' gives one actionable usage cue tied to a parameter, but there is no guidance on when to pick this tool over site_performance, opportunities or rank_tracking, and no stated preconditions such as needing 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.