Keytomic

Get AI visibility

get_visibility

Read-only

Returns the AI Search Visibility of a site, the same data as the AI Visibility page, in sections. Pass sections to pick them; without it, the tool returns overview only. The result has one key for each section and visibilityUrl, where the user opens the AI Visibility page. It starts nothing: no check, no setup and no observations. overview: whether the brand profile review is complete, the market (locale), the settings (AI platforms and UTC run days), the limits of the plan (Active and saved prompts, AI platforms, run days), the server schedule, the setup status, and nextRunAt, the next scheduled check. check (on request): the check overview: the observations a check needs, used and left this month, the available AI platforms, canStart and blockedReason, firstCheckNeeded and latestCheck. It can read the Google AI Mode locations and languages from DataForSEO. prompts (on request): the prompts of the site’s market with their promptId, text, topic, intent, type, state and revision. Without promptState it leaves out Archived prompts; pass promptState for the prompts of one state. suggestions (on request): the Suggested prompts of the setup, best first, with activeSlotsLeft, the Active prompts the plan allows and the Active prompts now. promptState needs the prompts section; an input the requested sections do not use gives invalid_arguments. When AI Visibility is off in this deployment, the call gives feature_disabled.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_visibility"
  }
}

Input Schema

Name	Required	Description
`sections`	No	Sections to return. Without it: overview. check, prompts and suggestions are returned only on request.
`projectId`	Yes	Site to act on, from list_sites.
`promptState`	No	With the prompts section: return only the prompts of this state. Without it, prompts leaves out Archived prompts.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating the call starts nothing. It goes further with error behavior an agent cannot get from annotations: invalid_arguments for inputs the requested sections do not use, and feature_disabled when AI Visibility is off in the deployment. Auth requirements and pagination are not addressed, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The default behavior is front-loaded correctly and every sentence is on-topic, but the single dense paragraph crams overview, check, prompts and suggestions into one unbroken block that is hard to scan. Splitting the per-section detail into a short list would improve it without losing content.

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 full burden of explaining return values, and it does so section by section (visibilityUrl, nextRunAt, canStart, blockedReason, prompt fields, activeSlotsLeft). Combined with the default and error behavior, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema handles the basics and a 3 is the floor. The description adds real meaning on top: it names what each section value yields, states that promptState requires the prompts section, and explains that omitting promptState drops Archived prompts. That is more than the schema states and justifies the bump.

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 states a specific verb and resource ('Returns the AI Search Visibility of a site... in sections') and equates it to the AI Visibility page, so the agent knows exactly what it gets. It does not mention the sibling get_visibility_report, so the boundary with that similarly named tool is left for the agent to infer.

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?

'Pass sections to pick them; without it, the tool returns overview only' plus 'check, prompts and suggestions are returned only on request' gives clear selection rules. 'It starts nothing: no check, no setup and no observations' implicitly routes to the start_* siblings, but no sibling is named, so there is context without explicit exclusions.

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

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

Resources

Need Help?