Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Share of voice from ranks

seo-content_share-of-voice-calc
Read-onlyIdempotent

Compute estimated clicks, visibility and share of voice per domain from rank snapshots, volumes and a caller-supplied CTR curve. Price $0.03 USDC. POST /api/v1/seo-content/share-of-voice-calc. 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": {
      "ctrCurve": "<ctrCurve>",
      "keywords": "<keywords>"
    },
    "name": "seo-content_share-of-voice-calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctrCurveYesctrCurve, array. Required.
keywordsYeskeywords, array. Required.

Output Schema

NameRequiredDescriptionDefault
tiesNoties. Array.
domainsNodomains. Array.
sourcesNosources. Array.
maxClicksNomaxClicks. Number.
limitationsNolimitations. 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?

The annotations already declare readOnly/idempotent/non-destructive/openWorld, yet the description adds genuinely non-obvious behavior: a $0.03 USDC price, the POST endpoint, and the critical detail that an unpaid call returns x402 payment terms and does not execute. It stops short of describing failure modes (e.g., curve length vs. max rank mismatch) or result shape, which is acceptable given an output schema exists.

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 sentences, front-loaded with the purpose, followed by commercial and availability facts. No filler, no restatement of the title, and the payment caveat is placed where it will be read before invocation.

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 a full output schema and rich annotations, the description covers purpose, cost, and payment gate, which is most of what an agent needs. The remaining gap is domain modeling—whether domains come from the ranks object keys and how strictly ctrCurve length must match possible rank positions—which the schema's auto-generated field text does not resolve.

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 baseline is 3. The phrase 'caller-supplied CTR curve' reinforces that ctrCurve comes from the caller, but nothing explains the single most ambiguous semantic: how array indices map to rank positions, or how the 'ranks' object keys relate to the 'per domain' output.

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?

The description opens with a specific verb and a precise output set: 'Compute estimated clicks, visibility and share of voice per domain from rank snapshots, volumes and a caller-supplied CTR curve.' That names both the computation and its three inputs, which lets an agent distinguish it from the neighboring analysis tools (rank-change-summary, keyword-opportunity-score) without opening the schema.

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 implied rather than stated: the agent can infer it applies when it holds rank snapshots plus volumes and wants a share-of-voice figure. There is no explicit when-to-use vs. a sibling alternative (e.g., rank-change-summary), and no stated preconditions such as requiring volumes for every keyword or the curve covering the full rank range.

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