Skip to main content
Glama

Visibility report (stub)

visibility.report

Reports Search Console visibility growth with deltas, trends, and ranked opportunities for 7d to 365d periods, using QualityKit Cloud connection settings.

Instructions

Search Console growth via QualityKit Cloud when QUALITYKIT_API_KEY + QUALITYKIT_API_BASE are set. Pass period 7d|28d|90d|365d for % deltas, trend, series summary, ranked opportunities, and changeOutcomes. Otherwise not_connected stub.

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": "visibility.report"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
apiKeyNoPro API key (or set QUALITYKIT_API_KEY env)
periodNoComparison window ending yesterday UTC (default 28d). Prior window is the same length before that.
apiBaseUrlNoQualityKit Cloud API base URL (or set QUALITYKIT_API_BASE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does the important part well: it discloses the two-mode behavior (connected data vs. not_connected stub) and the credential dependency, which prevents the agent from misreading an empty result. It does not cover rate limits, error shapes, or whether request-level apiKey overrides the env var.

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?

Two tight sentences, with the credential gating and the stub fallback front-loaded before the output list. Some density tips into jargon — 'changeOutcomes' is never glossed — but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The dual-mode behavior is the critical thing an agent needs and it is covered, but with no output schema the description should characterize the return shape more concretely than a list of unlabeled field names. The unexplained 'changeOutcomes' and the undocumented 'note' parameter leave real gaps for a 4-parameter tool.

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 75%, so the schema already documents apiKey, apiBaseUrl, and the period window semantics. The description restates the period enum values and the env-var fallbacks, adding little beyond the schema, and says nothing about the fourth parameter 'note', which is undocumented in both places.

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 definition names a concrete resource ('Search Console growth') and enumerates what the report yields: % deltas, trend, series summary, ranked opportunities, and changeOutcomes. It is specific enough to distinguish from siblings like opportunities.list, though the leading phrase is descriptive rather than a crisp verb+object pair.

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?

It states the prerequisite condition (QUALITYKIT_API_KEY + QUALITYKIT_API_BASE must be set) and the fallback (not_connected stub), which is real when-to-use guidance. However, it never routes the agent to an alternative when disconnected, and gives no guidance on choosing this over opportunities.list for the ranked-opportunities portion.

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