Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Brand mentions on the web (Brave Search)

brand_mentions
Read-onlyIdempotent

Search the web for brand mentions outside your domain, detect unlinked mentions as outreach targets, and view context excerpts to understand how AI engines see your brand.

Instructions

Search the web for pages mentioning a brand name that are not on your own domain, and check whether each mentioning page links to you. Unlinked mentions are outreach targets; the excerpts show in what context AI engines see the brand. Use freshness='pw'/'pm' to monitor only new mentions and offset to page past the first 20. Requires BRAVE_API_KEY (pay-as-you-go, about $5 per 1000 requests with ~$5 of free monthly credits: https://brave.com/search/api/).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes
countNoResults per page (max 20).
domainYesYour domain, excluded from results and used to detect links.
offsetNoResult page to fetch (0 = first 'count' results, 1 = next, up to 9): how to reach beyond the first 20 mentions.
countryNoes
languageNoen
freshnessNoOnly pages discovered in the past day / week / month / year. Leave unset for all time.
checkLinksNo
extraSnippetsNoAsk Brave for up to 5 excerpts per result so you can read what is said about the brand, not just that it is mentioned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / count / description
      Added value: +"Results per page (max 20)."
    • addedInput schema / properties / extraSnippets
      Added value: +{
+  "default": true,
+  "description": "Ask Brave for up to 5 excerpts per result so you can read what is said about the brand, not just that it is mentioned.",
+  "type": "boolean"
+}
    • addedInput schema / properties / freshness
      Added value: +{
+  "description": "Only pages discovered in the past day / week / month / year. Leave unset for all time.",
+  "enum": [
+    "pd",
+    "pw",
+    "pm",
+    "py"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Result page to fetch (0 = first 'count' results, 1 = next, up to 9): how to reach beyond the first 20 mentions.",
+  "maximum": 9,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed1 schema field changedv0.5.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints, so the bar is lower. The description adds valuable behavioral context: it requires an external BRAVE_API_KEY, explains the pay-as-you-go cost model, and clarifies that results exclude your own domain and include link detection plus excerpts.

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 pack the core purpose, key parameter guidance, and the critical API-key requirement without redundancy. The most important behavioral facts are front-loaded, and every sentence earns its place.

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?

For a 9-parameter tool with no output schema, the description covers the essential invocation details: required brand/domain, pagination, freshness, and external API key. It does not describe the exact return shape, but the purpose and key behaviors are sufficiently clear for an agent to call it 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 description coverage is 56%, with brand, country, language, and checkLinks lacking descriptions. The description helps by clarifying brand ('brand name'), domain exclusion, freshness monitoring, and pagination, but it does not compensate for the undocumented country/language parameters or fully detail checkLinks semantics.

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?

States a specific verb and resource: 'Search the web for pages mentioning a brand name that are not on your own domain, and check whether each mentioning page links to you.' This clearly differentiates the tool from siblings like ai_citation_check or ai_search_sources by focusing on brand mentions and outbound link detection.

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?

Provides concrete use cases: 'Unlinked mentions are outreach targets' and 'excerpts show in what context AI engines see the brand.' It also gives operational guidance for freshness and offset pagination, though it does not explicitly name alternative tools or state when not to use it.

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

Deploy Server

Other Tools