Skip to main content
Glama
Akxan

google-seo-mcp

by Akxan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check AI answer citations (Perplexity)

ai_citation_check
Read-onlyIdempotent

Determine if your domain is cited by AI search by submitting a customer question and reviewing the cited sources.

Instructions

Ask Perplexity's Agent API a question a customer might ask and report which sources it cites, whether your domain is among them, and the answer text. Useful to see if the site is being cited by AI search for target queries. Requires PERPLEXITY_API_KEY (paid, cents per call). ChatGPT and Google AI Overviews have no such API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesYour domain to look for in the citations, e.g. 'example.com'.
effortNoSearch effort: fast is the cheapest and closest to a plain AI answer; medium researches over several steps.fast
countryNoOptional 2-letter country code for localized search, e.g. 'ES', 'US'.
questionYesA natural question, e.g. 'What is the best guided walking tour in Seville?'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / effort
      Added value: +{
+  "default": "fast",
+  "description": "Search effort: fast is the cheapest and closest to a plain AI answer; medium researches over several steps.",
+  "enum": [
+    "fast",
+    "low",
+    "medium"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / model
      Removed value: -{
-  "default": "sonar",
-  "enum": [
-    "sonar",
-    "sonar-pro"
-  ],
-  "type": "string"
-}
  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 readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable operational context: it requires PERPLEXITY_API_KEY and costs cents per call, which is critical for an agent deciding whether to invoke the tool. It also clarifies it's an external API call. No contradictions with annotations.

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?

The description is exactly three sentences, each with a distinct purpose: function, use case, and requirements/cost. It is front-loaded with the core action and contains zero filler. Every sentence earns its place, making it highly efficient.

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 4-parameter tool with no output schema, the description covers the purpose, required inputs, output (citations, domain presence, answer text), API key requirement, and cost. It does not detail error handling or response formatting, but given the annotations cover safety and the output is explicitly described, it is largely complete for an agent to invoke 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 100% – all four parameters are already described in the schema. The description ties 'question' and 'domain' together conceptually ('a question a customer might ask', 'whether your domain is among them'), but adds no additional syntax, formatting, or edge-case details beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific action (ask Perplexity's Agent API a question) and a specific resource (Perplexity's Agent API), and clearly enumerates the outputs: sources cited, whether your domain is among them, and the answer text. It also differentiates from alternatives by noting that ChatGPT and Google AI Overviews have no such API, making the tool's scope unambiguous.

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?

The description gives clear context for when to use it: 'Useful to see if the site is being cited by AI search for target queries.' It also notes the limitation that only Perplexity offers this API, implying you cannot check other AI search platforms. It doesn't name a specific sibling tool as an alternative, but the context is sufficient for most agents.

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