Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_discover_history

Fetches daily Google Discover trend data as click and impression series with missing days filled as zero, ready to chart, plus point count and an insufficient_history flag.

Instructions

The daily Discover trend: two series, clicks and impressions, as {date, value} points with missing days back-filled with 0 and ready to chart, plus the number of points and an insufficient_history flag.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.4/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 disclose meaningful behavior: gaps are back-filled with 0 and an insufficient_history flag signals a thin dataset. Both are important because zero-filled days can be misread as true zeros. It does not state the default time window, retention limits, or any access requirements.

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?

A single sentence that front-loads the resource ('daily Discover trend') before the output shape. It is dense but every clause carries information; the only cost is that it reads as one long run-on rather than being split into purpose and return-value sentences.

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?

With no output schema, the description deserves credit for specifying the return shape, the point count, and the insufficient_history flag. But for a history tool it omits the single most operationally important fact: the time window covered and its granularity relative to now.

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?

The tool takes zero parameters, so the schema cannot be enriched and the baseline should be a 4. However, a zero-parameter history tool leaves a real question open: what date range is returned and can it be controlled at all? The description never resolves that, so it falls slightly below the zero-param baseline.

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?

States a specific resource and scope: the daily Discover trend, with two named series (clicks, impressions) rendered as {date, value} points. That is enough to distinguish it from summary/top-pages siblings by implication, but it never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of get_discover_summary or get_discover_top_pages. The 'history'/'trend' framing implies a time series, but the agent gets no criteria for choosing this over the summary tool.

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