AutoRank MCP

check_title_length

Measure page title pixel width to see if Google will truncate it. Obtain the estimate, limit, and verdict for optimal SEO titles.

Instructions

Check whether a page title will be truncated in Google results.

Measures approximate pixel width rather than character count, because Google truncates on width. Returns the estimate, the limit, and a verdict.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "check_title_length"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the measurement method (approximate pixel width instead of character count), the reason (Google truncates on width), and the return values (estimate, limit, verdict). This is genuinely transparent for a non-destructive check tool.

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?

The description is two sentences, front-loaded with the primary action, then a concise explanation of method and output. Every word earns its place with no redundancy.

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?

The tool is simple: one parameter, output schema exists, and the description covers purpose, method, and result. No additional context (such as authentication or rate limits) is necessary for a check tool like this. The description is fully complete for the tool's complexity.

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 has zero description coverage for the 'title' parameter, but the description compensates by identifying it as 'a page title' and explaining that it will be measured for width. This gives enough meaning for an agent to pass the correct value.

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 uses a specific verb and resource: 'Check whether a page title will be truncated in Google results.' This clearly distinguishes it from siblings like check_description_length (which checks meta descriptions) and serp_preview (which previews the entire SERP).

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 use case is clearly implied: use this tool to verify if a page title will be truncated in Google search results. The Google-specific context provides clear placement among alternatives, though it doesn't explicitly name any exclusions or alternative tools.

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

Deploy Server