Kampalo

AI search visibility

search_get_ai_visibility

Read-only

AI search visibility: how often AI models name and link the brand when asked the property's buyer questions, a 0-100 score with its parts, per-model results, competitor share of voice and the questions where competitors are named but the brand is not. Use for "do AI assistants recommend us" or GEO / AEO visibility.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_get_ai_visibility"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`days`	No
`limit`	No
`action`	No
`status`	No
`date_to`	No
`page_id`	No
`sort_by`	No
`user_id`	No
`site_url`	No
`client_id`	No
`date_from`	No
`ad_account`	No
`ig_user_id`	No
`user_email`	No
`range_preset`	No
`activity_only`	No
`campaign_name`	No
`property_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral content about what the report breaks down (per-model, share of voice, competitor-only questions), but says nothing about defaults, date-range behavior, or what happens when url/days are omitted.

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?

Front-loaded with what the tool produces, followed by one usage sentence — no filler. The first sentence is long and clause-heavy, but every clause describes a distinct output component.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and the description does cover output content well. But with 19 optional, entirely undocumented parameters and no guidance on defaults or identifier choice, the definition leaves an agent unable to construct a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 19 parameters at 0% schema description coverage, and the description explains none of them. Critical ones like url, site_url, property_name, days, limit, action, status, sort_by, and range_preset are completely undocumented anywhere, so an agent cannot know which identifier form to pass or what the values mean.

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?

The description names the specific resource (AI search visibility) and enumerates exactly what the report contains: a 0-100 score with its parts, per-model results, competitor share of voice, and gap questions. It is clear what the tool returns, but it never distinguishes itself from near siblings like analytics_get_ai_referrals or search_get_metrics, leaving the agent to infer which one answers an AI-visibility question.

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?

It offers a use context via quoted user phrasings and the GEO/AEO framing, which implies when to reach for it. However there are no exclusions and no named alternative, which matters here because analytics_get_ai_referrals sits right next to it and plausibly answers a related question.

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

All Kampalo 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.