serp-metrics

Share of voice across a keyword set

share_of_voice

Compute share of voice across competing entities over a keyword set. Reports impression share always, and, if you supply a CTR curve, a weighted visibility share that accounts for the fact that an impression at position 1 is not worth an impression at position 9. Impression share is share of the supplied set only and says nothing about keywords you did not supply.

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": {
      "entities": "<entities>"
    },
    "name": "share_of_voice"
  }
}

Input Schema

Name	Required	Description	Default
`entities`	Yes	One entry per competitor per keyword, or pre-aggregated per competitor.
`ctr_curve`	No	Optional caller-supplied position-to-CTR map, for weighted visibility.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It clearly states the always-on metric, the conditional weighted metric, and the interpretation caveat. It also explains the rationale for weighting (position 1 vs 9). It stops short of describing output structure or error cases, but the core behavior is transparent.

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?

Two sentences, front-loaded with the main action, then conditional behavior, then an important limitation. Every sentence contributes meaning; no 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?

The tool has a moderate complexity with nested parameters and no output schema. The description covers the input semantics and the two possible metrics returned, and warns about the scope limitation. It doesn't detail the return format but that is not strictly required for a computation tool. It is reasonably complete for an agent to select and invoke correctly.

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?

Although schema coverage is 100%, the description adds meaning by explaining the function of the CTR curve and clarifying that entities can be per-keyword or pre-aggregated per competitor. It also explains when position is needed (when a CTR curve is supplied), which aligns with the schema.

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 uses the specific verb 'Compute' with the resource 'share of voice across competing entities over a keyword set', clearly distinguishing it from sibling tools focused on position weighting and click projection. It also specifies the exact metrics computed (impression share and optional weighted visibility share).

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

Usage Guidelines4/5

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

It identifies a clear condition for using the weighted mode ('if you supply a CTR curve') and cautions that impression share is relative only to the supplied set. It does not explicitly name sibling tools as alternatives, but provides enough context to decide when to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All serp-metrics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?