Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

View AI visibility

get_visibility
Read-only

Use this when the user asks whether they show up in ChatGPT, Gemini, Perplexity or Google AI Overviews, or about AI visibility, GEO or AI search, or their standing orders call for it. Returns, for each tracked customer question, which engines name the product, plus the questions where competitors are named instead, the most cited sources, share of voice, the trend and the off-site reach fold. prompt_id returns one question's answers, competitors and citations. A change is indicative unless the sampling block says otherwise. Read-only, free.

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_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_idNoDrill into one tracked question by its id (from the prompts list) for the engine answer text and citations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt_id / description
      Previous value: -"Optional: drill into one tracked question by its id (from the prompts list) for the full engine answer text and citations."New value: +"Drill into one tracked question by its id (from the prompts list) for the engine answer text and citations."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint false and openWorldHint false, and the description reinforces this with 'Read-only, free.' Beyond that it adds a meaningful caveat ('A change is indicative unless the sampling block says otherwise') and enumerates what the response contains, which the annotations do not cover.

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 the trigger condition, then the return contents, then the drill-down, then a safety/quality note. It is dense and every clause carries information, though the run-on list of return fields ('share of voice, the trend and the off-site reach fold') is slightly hard to parse.

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?

There is no output schema, so the description needs to describe returns, and it does so thoroughly enough for an agent to know what to expect. The only gap is the opaque term 'the off-site reach fold', which is left undefined.

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 baseline is 3. The description adds genuine meaning to prompt_id by explaining it returns one question's answers, competitors and citations, clarifying the scoped versus full-report behavior.

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 names a specific verb and resource ('show up in ChatGPT, Gemini, Perplexity or Google AI Overviews') and frames the tool as the AI-visibility report. An agent can distinguish this from siblings like get_seo or get_competitors without needing to inspect any schema.

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 gives concrete triggering conditions ('user asks whether they show up in...', 'AI visibility, GEO or AI search', 'standing orders call for it'), which is strong when-to-use guidance. It does not name an alternative sibling or an explicit when-not, though the prompt_id sentence implies the drill-down path.

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

All AfterLaunch toolsInspect
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