SEO Score API

AI Citation Starter Prompts

citation_starter_prompts

Read-onlyIdempotent

Build a starter set of prompts to track for AI citations, from a topic plus optional brand, competitors and audience. Fixed templates, not a model: no AI check is spent. Works on every plan and is not metered. Returns prompts, ready to pass to create_citation_tracker.

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": {
      "topic": "<topic>"
    },
    "name": "citation_starter_prompts"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Your brand name (optional).
`limit`	No	Cut the list to this many (1-60).
`topic`	Yes	What you sell, as a buyer would type it, singular (e.g. "SEO audit API").
`audience`	No	Who buys it, plural (e.g. "marketing agencies").
`features`	No	Up to 6 features buyers ask about.
`use_cases`	No	Up to 6 jobs it is bought for.
`competitors`	No	Up to 5 competitor names.
`per_category`	No	Prompts per category, 1-10 (default 2 = 12 prompts).

Output Schema

Name	Required	Description	Default
`prompts`	No	Prompts ready for create_citation_tracker.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds value beyond them by disclosing the cost model (no AI check, unmetered, all plans) and that output is deterministic template generation rather than model inference. Return shape is left to the output schema, which exists.

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 compact sentences, front-loaded with the action and followed by cost and handoff information; nothing is padded. Minor redundancy between "no AI check is spent" and "is not metered" keeps it just short of ideal.

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 eight parameters, one required, full schema coverage, an output schema and non-destructive annotations, the description covers the gaps that matter: cost, determinism and the downstream tool. Only the choice against the AI-suggestion sibling remains unaddressed.

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 100%, so all eight parameters, including limit, per_category, features and use_cases, are already documented with constraints. The description restates only topic, brand, competitors and audience, adding no meaning beyond the schema; baseline 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?

"Build a starter set of prompts to track for AI citations, from a topic plus optional brand, competitors and audience" names a specific verb (build) and resource (prompt set), and lists the key inputs. "Fixed templates, not a model" implicitly separates it from the AI-driven sibling citation_suggest_prompts, though that sibling is never named.

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?

Gives clear usage context: it is free on every plan, unmetered, and consumes no AI credits, and it states the downstream step ("ready to pass to create_citation_tracker"). It does not explicitly say when to prefer this over citation_suggest_prompts or when a starter set is insufficient.

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

All SEO Score API tools Inspect

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.