Skip to main content
Glama

Get my AI visibility

get_ai_visibility
Read-onlyIdempotent

How often AI answers name the member's brand (visibility), recommend it, where it ranks (position) and the tone (sentiment), with change vs the previous period; the brand standings against tracked competitors; per-model visibility (ChatGPT, Google AI Mode, AI Overviews…); what AI praises and criticizes; brands AI names that aren't tracked. Same numbers as Kliqo's Answer audit and Insights. Use for "how visible are we in ChatGPT?", "who is winning?", "what does AI say about us?". Needs sign-in to Kliqo (read-only).

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": "get_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOnly this AI model's answers; leave out for the project's current models
rangeNoDate range, ending today in the project's time zone30d
projectNoProject name, domain or id; leave out for the workspace's current project
end_dateNoExact end date (YYYY-MM-DD), today at the latest
start_dateNoExact start date (YYYY-MM-DD), for example the 1st of a month; use with end_date instead of range

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that by stating that sign-in to Kliqo is required and that the numbers match Kliqo's Answer audit and Insights. It does not cover pagination, quotas, or empty-result behavior, but with rich annotations and an output schema the added detail is meaningful.

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?

The description is front-loaded and dense with useful selection information, and each major clause contributes to explaining the metric set or usage. It is somewhat long and enumerates return areas even though an output schema exists, but it remains readable and purposeful.

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?

Given the rich annotations, complete parameter schema, and existing output schema, the description provides enough context for correct invocation: it explains the metric scope, example use cases, and the authentication requirement. No critical calling information is missing.

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?

The input schema has 100% description coverage and documents every parameter, including enums and defaults. The description does not add parameter-specific syntax or selection guidance beyond what the schema already provides, so the baseline score of 3 applies.

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 gives a specific, detailed account of what the tool returns: visibility, recommendation, position, sentiment, competitor standings, per-model visibility, praise/criticism, and untracked brands. It is clearly a visibility-analytics tool rather than a raw answer-retrieval tool, but it does not explicitly name or rule out sibling tools such as get_answers or get_competitor_gaps.

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?

It supplies clear example use cases ("how visible are we in ChatGPT?", "who is winning?", "what does AI say about us?") and notes the sign-in requirement. However, it does not explicitly say when to prefer this over alternatives or 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources