OnlineCyberTools MCP (280+ filterable tools)

seo_title_description_length_checker

Read-onlyIdempotent

Check SEO title and meta description lengths against Google SERP pixel limits. Get truncation preview, score, and suggestions to avoid cut-offs in search results.

Instructions

SEO Title and Meta Description Length Checker. Analyze an HTML title tag and meta description against Google SERP display limits, estimating rendered pixel width (Arial 18px title, Arial 13px description) rather than raw character count, since Google truncates by pixels. Reports char/word counts, estimated pixel width, the truncation point and truncated preview (with ellipsis), a within-limits flag, a 0-100 score, severity-tagged warnings, and cross-field suggestions for desktop or mobile. Use this to audit or proof an existing snippet before publishing; use seo_meta_tag_generator to build the meta tags themselves, or seo_keyword_density_checker to analyze body content. Runs locally on the text you provide (read-only, non-destructive, contacts no external service) and is rate-limited (30 requests per minute for anonymous callers). Returns a per-field analysis object for title and description plus a suggestions list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	No	Operation to run. Only analyze is supported; omit to default to it.	analyze
`title`	Yes	The HTML title tag text to check. Required and must not be blank. Max 10000 characters.
`description`	Yes	The meta description text to check. Required and must not be blank. Max 10000 characters.
`brand`	No	Optional brand name. If supplied and it gets truncated out of the visible title, a suggestion advises moving it to the front.
`brandSuffix`	No	Optional trailing brand suffix (for example a pipe then Acme). If the title ends with it, the tool flags how many chars it consumes.
`device`	No	Which SERP layout to measure against. Mobile uses narrower pixel limits. Any value other than mobile is treated as desktop.	desktop

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	Whether the analysis succeeded.
`operation`	No	The operation performed (always analyze).
`result`	No	The analysis payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / brand / description

Added value: +"Optional brand name. If supplied and it gets truncated out of the visible title, a suggestion advises moving it to the front."

addedInput schema / properties / brandSuffix / description

Added value: +"Optional trailing brand suffix (for example a pipe then Acme). If the title ends with it, the tool flags how many chars it consumes."

addedInput schema / properties / description / description

Added value: +"The meta description text to check. Required and must not be blank. Max 10000 characters."

addedInput schema / properties / device / default
```
Added value: +"desktop"
```

addedInput schema / properties / device / description

Added value: +"Which SERP layout to measure against. Mobile uses narrower pixel limits. Any value other than mobile is treated as desktop."

addedInput schema / properties / device / enum

Added value: +[
+  "desktop",
+  "mobile"
+]

addedInput schema / properties / operation

Added value: +{
+  "default": "analyze",
+  "description": "Operation to run. Only analyze is supported; omit to default to it.",
+  "enum": [
+    "analyze"
+  ],
+  "type": "string"
+}

addedInput schema / properties / title / description

Added value: +"The HTML title tag text to check. Required and must not be blank. Max 10000 characters."

changedInput schema / required

Previous value: -[
-  "title",
-  "description",
-  "brand",
-  "brandSuffix",
-  "device"
-]New value: +[
+  "title",
+  "description"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "operation": {
+      "description": "The operation performed (always analyze).",
+      "type": "string"
+    },
+    "result": {
+      "description": "The analysis payload.",
+      "properties": {
+        "description": {
+          "description": "Length/pixel analysis for the description field (same shape as title).",
+          "properties": {
+            "charLength": {
+              "description": "Character count of the description.",
+              "type": "integer"
+            },
+            "pixelLimit": {
+              "description": "Google display pixel limit for this field and device.",
+              "type": "integer"
+            },
+            "pixelWidth": {
+              "description": "Estimated rendered width in pixels.",
+              "type": "integer"
+            },
+            "score": {
+              "description": "A 0-100 quality score for this field.",
+              "type": "integer"
+            },
+            "text": {
+              "description": "The submitted description text.",
+              "type": "string"
+            },
+            "truncated": {
+              "description": "Whether the text exceeds the pixel limit.",
+              "type": "boolean"
+            },
+            "truncatedText": {
+              "description": "Visible portion before truncation (no ellipsis).",
+              "type": "string"
+            },
+            "truncatedTextWithEllipsis": {
+              "description": "Visible portion with a trailing ellipsis if truncated.",
+              "type": "string"
+            },
+            "truncationPoint": {
+              "description": "Character index where Google likely cuts the snippet.",
+              "type": "integer"
+            },
+            "warnings": {
+              "description": "Field-specific warnings.",
+              "items": {
+                "properties": {
+                  "message": {
+                    "description": "Human-readable warning text.",
+                    "type": "string"
+                  },
+                  "severity": {
+                    "description": "Warning severity (critical, high, medium, low, or info).",
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "withinLimits": {
+              "description": "Whether the text fits recommended length and is not truncated.",
+              "type": "boolean"
+            },
+            "wordCount": {
+              "description": "Whitespace-delimited word count.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "device": {
+          "description": "The SERP layout analyzed (desktop or mobile).",
+          "type": "string"
+        },
+        "suggestions": {
+          "description": "Cross-field improvement suggestions.",
+          "items": {
+            "properties": {
+              "field": {
+                "description": "Target field (title, description, or general).",
+                "type": "string"
+              },
+              "message": {
+                "description": "Human-readable suggestion text.",
+                "type": "string"
+              },
+              "severity": {
+                "description": "Suggestion severity (critical, high, medium, low, or info).",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "title": {
+          "description": "Length/pixel analysis for the title field.",
+          "properties": {
+            "charLength": {
+              "description": "Character count of the title.",
+              "type": "integer"
+            },
+            "pixelLimit": {
+              "description": "Google display pixel limit for this field and device.",
+              "type": "integer"
+            },
+            "pixelWidth": {
+              "description": "Estimated rendered width in pixels.",
+              "type": "integer"
+            },
+            "score": {
+              "description": "A 0-100 quality score for this field.",
+              "type": "integer"
+            },
+            "text": {
+              "description": "The submitted title text.",
+              "type": "string"
+            },
+            "truncated": {
+              "description": "Whether the text exceeds the pixel limit.",
+              "type": "boolean"
+            },
+            "truncatedText": {
+              "description": "Visible portion before truncation (no ellipsis).",
+              "type": "string"
+            },
+            "truncatedTextWithEllipsis": {
+              "description": "Visible portion with a trailing ellipsis if truncated.",
+              "type": "string"
+            },
+            "truncationPoint": {
+              "description": "Character index where Google likely cuts the snippet.",
+              "type": "integer"
+            },
+            "warnings": {
+              "description": "Field-specific warnings.",
+              "items": {
+                "properties": {
+                  "message": {
+                    "description": "Human-readable warning text.",
+                    "type": "string"
+                  },
+                  "severity": {
+                    "description": "Warning severity (critical, high, medium, low, or info).",
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "withinLimits": {
+              "description": "Whether the text fits recommended length and is not truncated.",
+              "type": "boolean"
+            },
+            "wordCount": {
+              "description": "Whitespace-delimited word count.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the analysis succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint; description adds 'Runs locally on the text you provide (read-only, non-destructive, contacts no external service)' and rate limit of 30 requests per minute for anonymous callers. No contradiction and adds meaningful context.

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?

Description is thorough but slightly lengthy; however, every sentence earns its place by adding purpose, usage, behavioral notes, or parameter semantics. It is well-structured and front-loaded.

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?

Given the tool's complexity (6 parameters, output schema exists), the description covers purpose, usage context, behavioral traits (read-only, rate-limited), parameter details, and output structure. It is fully complete for an agent to decide and use correctly.

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

Parameters5/5

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

Schema coverage is 100% with descriptions for all 6 parameters. Description adds value by explaining the pixel width estimation (Arial font sizes), the purpose of brand and brandSuffix parameters, and details of the output (chars, words, pixel width, truncation point, score, warnings, suggestions). This goes beyond schema.

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 clearly states the tool analyzes title and meta description lengths against Google SERP pixel limits, with specific verb 'analyze' and resource 'HTML title tag and meta description'. It differentiates from sibling tools seo_meta_tag_generator and seo_keyword_density_checker by explicitly stating what each does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use ('audit or proof an existing snippet before publishing') and when not to (for building tags, use seo_meta_tag_generator; for body content, use seo_keyword_density_checker). Also notes rate limiting and read-only nature.

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

Deploy Server