Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Heading outline gap analysis

seo-content_heading-outline-compare
Read-onlyIdempotent

Compare a target H1–H6 outline with competitors and list common sections the target lacks. Price $0.03 USDC. POST /api/v1/seo-content/heading-outline-compare. 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": {
      "target": "<target>",
      "competitors": "<competitors>"
    },
    "name": "seo-content_heading-outline-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYestarget, object. Required.
minShareNominShare, number, from 0 to 1. Required.
competitorsYescompetitors, array. Required.

Output Schema

NameRequiredDescriptionDefault
missingNomissing. Array.
sourcesNosources. Array.
warningsNowarnings. Array.
targetOnlyNotargetOnly. Array.
limitationsNolimitations. Array.
targetOutlineNotargetOutline. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description still adds genuinely useful non-obvious context: a $0.03 USDC price, the POST endpoint, and the critical fact that an unpaid x402 call returns payment terms and does not execute. It stops short of noting limits such as maximum competitor count or failure modes.

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 tight sentences, front-loaded with the outcome, then the commercial/transport facts. Nothing is repeated from the schema or annotations and no sentence is filler.

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?

An output schema exists, so return-value explanation is unnecessary, and the payment/transport behavior is disclosed. The only shortfall is unexplained threshold semantics for minShare and no indication of practical bounds (competitor array size, HTML length expectations) for a nested-object payload.

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 the schema already documents all three parameters, including nested url/html fields. However, the description never explains minShare, the 0–1 threshold that determines what counts as a 'common' section — a semantically loaded parameter an agent would benefit from understanding.

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?

States a specific verb and resource ('Compare a target H1–H6 outline with competitors') plus the concrete output ('list common sections the target lacks'). The heading-outline resource distinguishes it from term-gap or topic-coverage siblings without needing to name them.

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 is only implied: the agent must infer that this is for post-crawl structural comparison of a page against competitor pages. No explicit when-to-use, when-not-to-use, or alternative routing (e.g., use term-gap for keyword-level gaps) is given.

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