Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_report

Retrieve a report’s metadata and complete widget structure—including types, titles, positions, configs, and filters—to inspect its composition, not rendered analytics numbers.

Instructions

Get one report's metadata (name, is_template, is_automate, owner, created_at, plus period and recipients when scheduled) and its full widget structure — every widget's type, title, position, config and filters. Returns the report's composition, not rendered analytics numbers (read those with the GSC / GA4 tools).

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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.3/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 well: it discloses the exact information returned, notes that period and recipients appear only "when scheduled" (conditional field presence), and clarifies that widget config and filters are included. The remaining gap is that it says nothing about read-only safety, size limits, or failure behavior for a nonexistent report, which for a no-annotation tool keeps it short of a 5.

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 sentences, front-loaded with the returned content and closing with the disambiguation clause, so the most decision-relevant information comes first. The long parenthetical field list is information-dense and earns its place, though it makes the first sentence heavy to scan.

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?

Since there is no output schema, the description must describe return values, and it does so concretely: metadata fields, conditional scheduling fields, and per-widget type, title, position, config, and filters. It is nearly complete for a simple no-parameter getter; only edge cases like missing reports or very large widget sets go unmentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics are trivially satisfied and the baseline of 4 applies. The description does not need to explain arguments, and it correctly spends its words on return content instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("Get one report's metadata") and immediately enumerates the fields returned (name, is_template, is_automate, owner, created_at, period, recipients) plus the full widget structure. It also explicitly distinguishes itself from the GA4/GSC analytics tools, so an agent can separate this from siblings like generate_report or get_ga4_summary without opening a schema.

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?

It gives a clear usage boundary: use this for report composition, and read rendered analytics numbers with the GSC / GA4 tools instead. That is an explicit routing instruction with a named alternative class. What is missing is guidance on when to prefer this over generate_report or how the single-report lookup relates to a listing tool, but the main exclusion is stated.

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

Deploy Server

Other Tools