Skip to main content
Glama

ADS Beast

aeo_visibility_scan

Read-only

How often AI models mention a client's brand for the queries of its niche: a 0-100 score, a per-model breakdown and the quotes. AI: 1 AI request. May return a job_id (get_job_result).

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": {
      "client_id": "<client_id>"
    },
    "name": "aeo_visibility_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
competitorsNoCompetitor names or domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). Beyond that, the description adds genuinely useful behavior: the call costs one AI request and may return asynchronously with a job_id that must be polled via get_job_result.

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?

Three short, front-loaded clauses: what it measures, what it returns, and the cost/async caveat. The telegraphic 'AI: 1 AI request' phrasing is slightly cryptic but conveys real information with no filler.

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?

With no output schema, the description correctly enumerates the return contents (score, per-model breakdown, quotes) and explains the async job flow. The remaining gap is the role of the optional competitors parameter, which is left unexplained for a two-parameter tool.

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 coverage is 50% — client_id has no description and only competitors ('Competitor names or domains') is documented. The description partially compensates by implying the client's niche drives the query set, but it never explains what supplying competitors changes in the scan.

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 measurement — how often AI models mention a client's brand for its niche queries — and names the return shape (0-100 score, per-model breakdown, quotes). It is clearly not a benchmark or content tool, though it does not explicitly contrast itself with sibling tools such as competitor_aeo_benchmark.

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: an agent can infer this is the tool for measuring AI visibility for a given client. The one explicit routing hint is that a returned job_id should be handled with get_job_result, but there is no stated when-not-to-use condition or prerequisite guidance.

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.