Skip to main content
Glama

AI Visibility Audit

Find prompts a brand could be cited for

find_prompt_opportunities
Read-onlyIdempotent

Read a site and suggest the questions people ask answer engines where this brand could plausibly be recommended — the prompts worth tracking and writing content for. Returns a shareable result page.

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": {
      "url": "<url>"
    },
    "name": "find_prompt_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to check, e.g. https://example.com or example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only two behavioral facts: it reads an external site and returns an online/shareable result page. It says nothing about runtime, failure on unreachable sites, or whether results are cached between calls.

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?

One sentence plus a short return-value clause, front-loaded with the action. The middle clause ('the questions people ask answer engines where this brand could plausibly be recommended') is dense and slightly hard to parse on first read, but nothing is wasted.

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

Completeness3/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 must convey what comes back, and 'a shareable result page' is thin — an agent cannot tell whether it receives a URL, a list of prompts, or a rendered HTML page. For a read-only, single-parameter tool the gaps are modest, but the return shape is under-described.

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 description coverage is 100% and the single url parameter already carries a format example, so the baseline applies. The description's phrase 'read a site' loosely reinforces what url means but adds no constraints beyond the schema's maxLength and example.

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?

States a concrete verb-and-resource pair: read a site and suggest the questions people ask answer engines where the brand could be cited. That is clearly distinct from sibling audit/schema-check tools, but the description never names an alternative to sharpen the contrast, so it lands just short of a 5.

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 gives an implied use case — prompts worth tracking and writing content for — which tells the agent why someone would call it. There is no explicit when-to-use versus when-not, no prerequisite such as the site being crawlable, and no sequencing advice relative to the readiness/audit siblings.

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