Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

serp_pixel_preview

Pixel-width SERP snippet preview with truncation for desktop and mobile

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

Input Schema

NameRequiredDescriptionDefault
urlNoDisplay URL
titleYesPage title
descriptionNoMeta description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the core behavior (pixel-width measurement and truncation across desktop and mobile), but says nothing about what the response contains, how truncation is signalled, what widths are assumed, or whether missing optional fields are handled gracefully. For a preview tool whose whole value is its output shape, this leaves a significant gap.

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?

A single front-loaded sentence with no filler; the scope qualifier (desktop and mobile) is placed where it is immediately visible. It is only slightly short of ideal because compactness here edges toward under-specification rather than tight precision.

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?

With three params, full schema coverage, and no output schema, the description should at least sketch what the preview returns and how truncation is presented. It covers the concept but not the result, which is the main missing piece for a simple render 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 url, title, and description are already documented as Display URL, Page title, and Meta description. The description adds no further meaning such as length expectations or what happens when description is omitted. Baseline 3 applies when the schema does the explaining.

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 names a specific capability: a pixel-width SERP snippet preview with truncation for desktop and mobile. That verb-plus-resource phrasing lets an agent tell it apart from the validation/audit siblings, which check issues rather than render a preview. It stops short of explicitly distinguishing itself from those siblings by name.

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 statement of when to use this tool, no preconditions, and no pointer to an alternative for related tasks such as length validation. The agent must infer usage entirely from the purpose phrase.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources