Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

generate_report

Create a shareable snapshot of an existing report and get its public URL. Captures the report's current widget state, so edit widgets first to change the period.

Instructions

Generate a shareable snapshot of an existing report and return its public URL (write action). Snapshots the report's current widget state, deduped by content hash — it takes no date range, so edit the report's widgets first if you need a different period. Returns report_id, snapshot_id and url.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.5/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 declares this is a write action, that a public URL becomes reachable, that the snapshot captures current widget state, and that snapshots are deduped by content hash (implying repeat calls may not create new snapshots). It stops short of stating permission/scope requirements or how the public link can be revoked.

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?

Three compact sentences, front-loaded with the action and side effect, then the precondition, then the return fields. Every clause carries information an agent needs; there is no filler or restatement of the name.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description supplies the mutation semantics, the dedupe behavior, the precondition, and the exact return fields (report_id, snapshot_id, url). An agent has everything required to invoke it correctly and interpret the result.

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?

There are zero parameters, so the baseline is 4, and the description correctly makes clear that no date range or other input is accepted. Nothing further about parameters is needed or added.

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 gives a specific verb and resource ('Generate a shareable snapshot of an existing report') plus the returned artifact ('public URL'), and labels it a write action. It is clearly distinguishable from read-side siblings like get_report, since it produces a snapshot rather than reading report data.

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 states a concrete precondition and exclusion: it takes no date range, so the agent must edit the report's widgets first if a different period is needed. It does not name a sibling alternative explicitly, but the when-to-use context is unambiguous.

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