Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

SERP snippet pixel-width preview

seo-content_serp-snippet-preview
Read-onlyIdempotent

Estimate title and meta description pixel widths with Liberation Sans advances and truncate at caller-chosen limits. Price $0.02 USDC. POST /api/v1/seo-content/serp-snippet-preview. An unpaid call returns the x402 payment terms and does not run.

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>",
      "description": "<description>"
    },
    "name": "seo-content_serp-snippet-preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYestitle, string, length 0 to 1000. Required.
titleMaxPxNotitleMaxPx, value. Optional.
descriptionYesdescription, string, length 0 to 5000. Required.
titleFontPxNotitleFontPx, number, from 8 to 40. Required.
descriptionMaxPxNodescriptionMaxPx, value. Optional.
descriptionFontPxNodescriptionFontPx, number, from 8 to 40. Required.

Output Schema

NameRequiredDescriptionDefault
fontNofont. String.
titleNotitle. Object.
sourcesNosources. Array.
estimateNoestimate. Boolean.
descriptionNodescription. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: a $0.02 USDC price, an x402 payment step where an unpaid call returns payment terms and does not execute, and the underlying rendering assumption (Liberation Sans advances). That payment/authorization disclosure is exactly the kind of context annotations cannot carry.

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?

Three short sentences, front-loaded with the capability, then cost/payment, then endpoint. No filler or repetition. The raw POST path is arguably redundant but harmless as a payment-routing cue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description needs only to cover the unusual parts, and it does: cost, x402 payment flow, and the measurement basis. Remaining gaps are minor, such as whether truncation inserts an ellipsis or what units the returned widths use, which the output schema likely covers.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining that truncation happens at caller-chosen limits, which clarifies what the otherwise mechanically documented titleMaxPx/descriptionMaxPx fields actually do. It also names the font-advance basis that gives titleFontPx/descriptionFontPx their significance. It stops short of explaining interaction between limits and fonts or what truncation output looks like.

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 states a specific verb and resource: estimating title and meta-description pixel widths with Liberation Sans font advances, plus truncation at caller-chosen limits. That is far more precise than the name alone. It does not explicitly distinguish itself from the SEO sibling tools, but the operation described is clearly disjoint from them, so the only deduction is the missing sibling differentiation.

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

Usage Guidelines3/5

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

Usage context is implied by the mechanics (you would call this to check how a title/description renders in a SERP and whether it gets cut off), but the description never states when to use this versus alternatives or any prerequisites beyond payment. The payment note tells the agent an unpaid call returns terms rather than a result, which is a useful operational cue, but there is no explicit when/when-not guidance.

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