SEO MCP Server

About this server

about

Check the server's version, loaded capabilities, Search Console connection status, and demo mode to diagnose why a tool might be missing.

Instructions

Version, credits and the current configuration — which capabilities are loaded, whether Search Console is connected, and whether demo mode is on. Useful when a tool is missing and you want to know why.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It implies a read-only informational call by listing version, credits, and configuration, but it never explicitly states that it has no side effects or does not modify state. For a simple about tool this is a minor gap.

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?

Two sentences, each earning its place: the first lists the informational contents, the second gives the practical diagnostic use case. No filler or repetition of the title.

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?

For a zero-parameter, low-complexity tool without an output schema, the description is sufficiently complete. It names the expected content areas and the scenario in which the tool is valuable. It could optionally note the exact return format, but that is not necessary for an about-style endpoint.

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 has zero parameters, so the description does not need to explain parameter usage. The baseline for no-parameter tools is 4, and the description satisfies it by explaining what information the call returns rather than mentioning irrelevant inputs.

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 description clearly identifies the resource (server info) and the specific content delivered: version, credits, current configuration, loaded capabilities, Search Console connection, and demo mode. It lacks an explicit verb like 'returns' or 'provides', but it is easy to distinguish from the sibling SEO-action tools.

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?

The description gives a concrete use case: 'Useful when a tool is missing and you want to know why.' This tells the agent when to invoke this tool. It does not discuss exclusions or alternatives, but no alternatives are really relevant for a server introspection tool.

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

Deploy Server