Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_code_monitor_snapshot

Fetch the current captured on-page SEO fields for a monitored page by seoMonitorId or URL to verify title, meta, robots, headings, status, and analytics signals.

Instructions

Get the most recent captured state of a monitored page — the current extracted on-page fields (title, canonical, meta description, meta robots, robots.txt, sitemap.xml, H1, headings, status code, hreflang, Open Graph image, Twitter image, Analytics, Tag Manager). Address the page by seoMonitorId or url; raw HTML and screenshots are not stored. Returns not_found for an unknown page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/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 two useful behavioral facts: raw HTML and screenshots are NOT stored, and an unknown page yields not_found. It omits permission/auth requirements and freshness semantics (how stale the captured state can be), which matter for a snapshot tool, but the negative constraints and error behavior are meaningful beyond the schema.

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 front-loaded sentence establishes the purpose before the field enumeration, and a short second clause adds the storage limitation and error case. The long field list is dense but each item is a distinct returned attribute, so little is wasted; a compacted list would read slightly better.

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 usefully enumerates returned fields, and with no annotations it covers the not-found case. However, for a zero-declared-parameter tool it leaves the actual argument shape ambiguous and says nothing about freshness or permissions, so an agent still has gaps before calling correctly.

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 schema declares zero properties, so the description is the only source of addressing semantics, and it names the two valid keys (seoMonitorId, url). It does not say whether the keys are mutually exclusive, required, or whether url must be normalized, so it falls short of fully documenting the calling convention.

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?

"Get the most recent captured state of a monitored page" states a specific verb and resource, and the parenthetical enumerates the exact extracted fields (title, canonical, meta robots, sitemap.xml, status code, hreflang, etc.). The emphasis on "most recent captured state" implicitly separates it from change/history siblings like get_code_monitor_change.

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?

The description supplies addressing guidance ("Address the page by seoMonitorId or url") and an error condition ("Returns not_found for an unknown page"), which implies when the call is appropriate. It never explicitly contrasts with get_code_monitor_change or get_page_detail, so the agent must infer that this returns a point-in-time snapshot rather than history.

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