Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Content brief from SERP page texts

seo-content_brief-from-serp-texts
Read-onlyIdempotent

Build a content brief from caller-supplied top-ranking HTML: common headings, word-count target, questions and recommended TF-IDF terms. Price $0.04 USDC. POST /api/v1/seo-content/brief-from-serp-texts. 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": {
      "pages": "<pages>"
    },
    "name": "seo-content_brief-from-serp-texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYespages, array. Required.
languageNolanguage, string. Required.en
termLimitNotermLimit, integer, from 1 to 100. Required.
minHeadingShareNominHeadingShare, number, from 0 to 1. Required.

Output Schema

NameRequiredDescriptionDefault
notesNonotes. Array.
sourcesNosources. Array.
questionsNoquestions. Array.
wordCountNowordCount. Object.
limitationsNolimitations. Array.
commonHeadingsNocommonHeadings. Array.
recommendedTermsNorecommendedTerms. Array.
duplicatesIgnoredNoduplicatesIgnored. 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?

Beyond the annotations, the description discloses the price ($0.04 USDC), the transport (POST /api/v1/seo-content/brief-from-serp-texts), and the important failure mode that an unpaid call returns x402 payment terms without running. That is real behavioral value the readOnly/idempotent hints do not convey, though limits such as the 200k-char HTML cap are left to the schema.

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 with the core purpose front-loaded, followed by the cost/endpoint and the payment-gating caveat. Every sentence carries load and nothing is repeated from the schema.

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 values need no explanation, and the payment and endpoint behavior is covered. The definition is nearly complete for a paid, read-only analysis tool; only the relationship to sibling analysis tools is left unstated.

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 language, termLimit, and minHeadingShare are already documented in the schema. The description only alludes to term output ('recommended TF-IDF terms') without tying it to termLimit or explaining how minHeadingShare affects 'common headings', so it adds little parameter-level meaning.

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 gives a specific verb and artifact ('Build a content brief') and enumerates the produced components: common headings, word-count target, questions, and TF-IDF terms. It also pins the input shape ('caller-supplied top-ranking HTML'), which implicitly separates it from keyword-only siblings such as tfidf-term-gap, though no sibling is named.

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 requirement for caller-supplied top-ranking HTML, but the description never states when to prefer this over related tools like tfidf-term-gap or topic-coverage-score, and offers no exclusions or prerequisites beyond the input type.

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