Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Rank change winners and losers

seo-content_rank-change-summary
Read-onlyIdempotent

Summarise winners, losers, new/lost keywords, top-3/top-10 crossings and volatility between rank snapshots. Price $0.03 USDC. POST /api/v1/seo-content/rank-change-summary. 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": {
      "snapshots": "<snapshots>"
    },
    "name": "seo-content_rank-change-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
segmentByNosegmentBy, array. Required.
snapshotsYessnapshots, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
segmentsNosegments. Array.
warningsNowarnings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts the annotations cannot express: a $0.03 USDC price, the POST endpoint, and crucially that an unpaid call returns x402 payment terms instead of executing — an agent needs this to interpret a non-result response.

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 tight sentences: capability first, then price/endpoint, then the payment failure mode. Every sentence carries information, though the endpoint path is arguably redundant for an agent that only needs the tool name.

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 not be explained, yet the description still signals which metrics come back. Combined with the payment/execution caveat and a fully documented schema, the definition covers what an agent needs to invoke it correctly; only cross-tool selection guidance is absent.

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 both parameters (snapshots, segmentBy) are already documented, and the description adds no syntax or format detail beyond them. It spends its words on output metrics rather than input semantics, leaving this at baseline.

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?

Uses a specific verb ('Summarise') plus a concrete resource and enumerates the exact outputs it produces: winners, losers, new/lost keywords, top-3/top-10 crossings, and volatility. An agent can tell this is a snapshot-comparison tool rather than a single-snapshot metric tool, though it never names a sibling to distinguish itself from.

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?

The phrase 'between rank snapshots' implies the required input and context (comparing at least two dated rank lists), but there is no explicit when-to-use/when-not guidance and no routing to alternatives among the fourteen sibling tools. Usage is inferable rather than stated.

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