Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

get_ai_search_visibility

Measure brand visibility, mention frequency, and sentiment across generative AI search engines for target buyer queries to identify visibility gaps.

Instructions

Measure brand visibility, mention frequency, and sentiment across generative AI engines (Claude, ChatGPT Search, Gemini) for target buyer queries.

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": {
      "domain": "<domain>"
    },
    "name": "get_ai_search_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesTarget domain (e.g., 'citecontext.com')
queriesNoOptional list of buyer-intent search queries to test
brand_nameNoBrand or product name to track

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about behavior: no note that this likely issues live queries to multiple external engines (latency/cost implications), no permission requirements, and no statement of what happens when 'queries' is omitted or how many queries are allowed. The only behavioral fact conveyed is the set of engines queried.

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?

A single front-loaded sentence with the core action first and the engine scope in parentheses; no filler, hedging, or redundant restatement of the name.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only source of context for a fairly complex multi-engine measurement tool, and it never indicates result shape (per-engine breakdown? aggregate score?) or cost/latency. It covers what is measured adequately but leaves an agent unable to anticipate the response.

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 description marginally reinforces the schema by framing 'queries' as buyer-intent queries and by identifying the engines, but it adds no syntax, formatting, defaults, or limits (e.g., max query count) beyond what the schema already states.

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 verb ('Measure') with concrete measured quantities (visibility, mention frequency, sentiment) and names the engine set (Claude, ChatGPT Search, Gemini). It reads clearly as a measurement/reporting tool distinct from source-attribution siblings like get_ai_search_cited_sources, though it never names a sibling to draw that contrast explicitly.

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 only implied: the 'target buyer queries' framing suggests a brand-monitoring scenario, but there is no when-to-use statement, no exclusion, and no pointer to alternatives such as get_ai_search_cited_sources or track_competitor_generative_gap. An agent must infer the selection rule from the sibling names alone.

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