Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Title scorer

ayrank_title_score
Read-only

Scores a page title from 0 to 100 across eight factors, including length, power words, numbers, emotion, and AI citability, with a tip for each factor to guide improvements.

Instructions

Use to score a page title from 0 to 100 on eight factors (length, power words, numbers, emotion, question format, readability, AI citability, uniqueness) with a tip per factor. It is a heuristic, not a measure of rankings or clicks. Reads no page.

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

Input Schema

NameRequiredDescriptionDefault
titleYesThe title to score, up to 300 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint=true annotation aligns with 'Reads no page', so the safety claim is consistent, not contradictory. Beyond annotations, it discloses the output shape (0-100, eight factors, a tip per factor) and explicitly frames the result as a heuristic rather than a ranking or click predictor, which meaningfully pre-empts likely misinterpretation.

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 short sentences with no filler, and the core action plus scoring dimensions lead. The final caveat is compact and relevant.

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?

With one required string parameter and no output schema, the description fills the gap by describing the return value and its interpretation. Nothing an agent needs in order to call this correctly is missing.

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

Parameters3/5

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

There is one parameter and schema description coverage is 100%, with the schema already documenting the title and its 300-character limit. The description adds no further parameter detail, so the baseline applies.

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 ('score a page title') and enumerates the eight scoring factors and the 0-100 output range, so an agent knows exactly what comes back. That scope is distinct from sibling checks like ayrank_alt_text or ayrank_heading_outline, which audit different page elements.

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 the use case directly ('Use to score a page title'), which is clear context without naming alternatives or exclusions. No sibling conflicts with this tool, so the absence of routing guidance costs little.

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