Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_serp_pixel_preview

Preview how a page title, URL, and meta description appear in desktop and mobile SERP snippets, including pixel-width truncation, to catch overlong SEO copy before publishing.

Instructions

[SEO & GEO Readiness] Pixel-width SERP snippet preview with truncation for desktop and mobile Measured p50 13 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://seo.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlNoDisplay URL
titleYesPage title
descriptionNoMeta description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose genuinely useful behavior beyond the schema: that truncation is applied and that results are produced separately for desktop and mobile, plus measured latency figures. It does not state that this is a side-effect-free computation, what fields the response contains (truncated text, pixel widths, per-device flags), or how the URL parameter affects output.

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?

The capability statement is front-loaded in the first clause, which is exactly right. The trailing latency and endpoint clauses are operational metadata that does not help an agent decide or invoke, so the text is slightly padded but not wasteful.

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?

This is a small pure-function tool with full schema coverage and no output schema, so it does not need much. Still, with no annotations and no return-value description, an agent cannot tell whether the response gives truncated strings, pixel measurements, or both per device — a gap that matters for a preview tool.

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?

Schema description coverage is 100%, so all three parameters are already documented; per the rubric this sets a baseline of 3. The description adds no meaning to any parameter — it never says that title is required, nor what practical limits govern title/description length or how the URL is used.

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?

"Pixel-width SERP snippet preview with truncation for desktop and mobile" states a specific mechanism (pixel-width measurement) and a specific output (truncated snippet per device), which is distinguishable from siblings like schema_org_validator or geo_readiness_composite. It is clear but does not explicitly contrast itself against any named alternative.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. The only signal is implied by the phrase "SERP snippet preview", leaving the agent to infer that this is a pre-publish check for title/meta length.

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