Skip to main content
Glama

SEO and Keyword Data API

Brand mentions on the web (up to 100)

brand_mentions
Read-onlyIdempotent

Web pages that mention a brand or keyword: up to 100 with URL, domain, date, sentiment (positive / negative / neutral with scores), the page's rating, page type, country, language and domain / page rank (no snippets or authors), from a web content index, $0.048 a call. Use when monitoring brand mentions or finding PR and link prospects. No mention is an empty answer, still charged. Bad input is a free 400; a data source failure is not charged. Price: $0.048 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "keyword": "<keyword>"
    },
    "name": "brand_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1-100. Default 20.
keywordYesThe brand or keyword (at most 80 characters, up to 10 words).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered. The description adds genuinely useful non-annotation context: an empty result is still billed, bad input is a free 400, source failure is not charged, and the x402 payment token must be passed in _meta. That is strong, but it is cost/plumbing disclosure rather than operational behavior such as result ordering or whether repeated calls return a stable set.

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?

The field inventory is front-loaded and the billing/error terms follow in short, scannable sentences. The price is stated twice ('$0.048 a call' then 'Price: $0.048 per successful call'), which is a small redundancy in an otherwise tight block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so by enumerating every field plus explicitly noting what is excluded (no snippets or authors). Billing outcomes and the payment mechanism are also covered, leaving nothing an agent needs to call this correctly.

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 coverage is 100%, so both parameters are already fully documented, and the baseline is 3. The description only echoes the ceiling ('up to 100') and the notion of 'brand or keyword' without adding format or syntax guidance beyond the schema's 80-character/10-word constraint.

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?

States a specific resource ('web pages that mention a brand or keyword') and enumerates the returned fields, so the agent knows exactly what comes back. 'From a web content index' implicitly separates it from SERP-style siblings like google_search or bing_search, but it never names llm_mentions, which is the closest ambiguous alternative.

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?

Gives two concrete use cases ('monitoring brand mentions or finding PR and link prospects'), which is real when-to-use guidance. It stops short of exclusions or naming alternatives — an agent choosing between this and llm_mentions or relevant_pages gets no routing signal.

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