Skip to main content
Glama
AutomateLab-tech

automatelab-ai-seo

Official

Test whether an AI engine would cite this page

score_test_citation
Read-only

Simulate whether an AI engine would cite your page for a specific query. Get a cite/no-cite verdict with verbatim excerpt and ranked improvements.

Instructions

Simulate would an AI engine cite this page for this query?. The host LLM role-plays the chosen engine (chatgpt / claude / perplexity / google_ai_overviews / any), reads the page content, and returns a cite/no-cite verdict with the verbatim excerpt it would surface plus ranked improvements.

Read-only when given url (one HTTP GET). Zero network when given text.

Primary path uses MCP sampling. If the host doesn't support sampling, falls back to a deterministic heuristic derived from score_citation_worthiness (overall_score + per-engine subscore must both clear thresholds). The result includes mode: "sampling" | "static_heuristic" so callers can tell which path ran.

When to use: pre-publish gut-check for a specific query, or auditing whether existing content earns citation surface. Distinct from score_citation_worthiness (deterministic 0-100 score) and audit_page (whole-page rubric); this returns a binary cite/no-cite verdict tied to one query.

Either url or text must be provided. target_query is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic URL to fetch and test. Either this OR `text` is required.
textNoRaw text/HTML to test directly. Either this OR `url` is required.
engineNoWhich engine to simulate. `any` (default) uses a generic AI-search persona. Specific engines tune the cite criteria (e.g. perplexity favors statistic-dense excerpts; google_ai_overviews favors schema + freshness).any
target_queryYesThe user query the engine is answering. Required. Example: `how to add JSON-LD to a Next.js app`.
respect_robotsNoIf true (default), respect robots.txt when fetching `url`. Ignored when `text` is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesWhich code path produced the result: MCP sampling (host LLM) or deterministic heuristic fallback.
engineYesWhich engine persona produced the verdict.
reasoningYesPlain-language explanation of the verdict.
confidenceYesHow likely a real engine is to surface this page (0-100).
would_citeYesBinary verdict: would the simulated engine cite this page for the query?
improvementsYesRanked, specific edits to improve citation probability.
target_queryYesThe query the engine simulation answered.
blocking_issuesYesConcrete reasons the page is (or is not) citable. Empty if would_cite=true and excerpt is clearly attributable.
citation_excerptYesIf would_cite=true, the 20-60 word verbatim excerpt the engine would surface; otherwise null.
Behavior5/5

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

Discloses read-only nature (one HTTP GET for url, zero network for text), the fallback to heuristic if sampling is unsupported, and the mode indicator in results. Adds significant value beyond annotations by explaining the dual execution paths.

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?

Well-structured with front-loaded main purpose. Every sentence adds value, covering fallback, usage, and parameters. Could be slightly shorter, but not wasteful. Good balance.

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?

Covers the simulation logic, fallback mechanism, engine simulation, and output contents (verdict, excerpt, improvements, mode). With an existing output schema, this is fully complete for the tool's complexity.

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 baseline is 3. The description adds meaning by explaining engine-specific tuning (e.g., perplexity favors statistic-dense excerpts), the mutual exclusivity of url and text, and the effect of respect_robots. This justifies a 4.

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 clearly states it simulates whether an AI engine would cite a page, returning a cite/no-cite verdict with an excerpt and improvements. It distinguishes from sibling tools like score_citation_worthiness and audit_page by specifying the binary verdict tied to a single query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: pre-publish gut-check for a specific query or auditing citation surface. Also implies when not to use by contrasting with deterministic scoring and whole-page rubric. Provides clear context and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AutomateLab-tech/ai-seo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server