Skip to main content
Glama
AgentSEO MCP Server

AgentSEO MCP Server

AgentSEO AI Visibility Prompt Set

agentseo_ai_visibility_prompt_set
Destructive

Build AI visibility prompt sets mapped to owned assets, platforms, competitors, and citations, with weekly action routing for AI search comparison planning.

Instructions

Build stable AI visibility prompt sets mapped to owned assets, platforms, competitors, citations, and weekly action routing. Uses AgentSEO credits; repeating the call can create new charged work.

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": {
      "target": "<target>",
      "category": "<category>",
      "topics": "<topics>"
    },
    "name": "agentseo_ai_visibility_prompt_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNoRequest a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true.
localeNoHuman-readable market or locale context for the prompt set, for example United States. Type: String. Minimum: 2 characters. Maximum: 80 characters. Default: "United States".United States
targetYesYour target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Minimum: 1 characters. Required.
topicsYesRelevant topics or themes associated with this target, page or prospect. Type: Array. Minimum: 1 items. Maximum: 40 items. Required.
cadenceNoRecommended comparison frequency for the prompt set; does not schedule or execute recurring checks. Type: String. Accepted values: "weekly", "biweekly", "monthly". Default: "weekly".weekly
audienceNoIntended reader or buyer group in plain language; do not include unnecessary personal data. Type: String. Maximum: 180 characters. Optional; no client default.
categoryYesProduct or market category used to construct relevant AI-visibility prompts. Type: String. Minimum: 1 characters. Maximum: 160 characters. Required.
personasNoAudience-role labels to vary the planned prompts by buyer context. Type: Array. Maximum: 20 items. Default: [].
platformsNoAI/search platforms to design prompts for; this plans prompts and does not run them on those platforms. Type: Array. Minimum: 1 items. Maximum: 6 items. Default: ["chatgpt","perplexity","google_ai"].
competitorsNoCompeting brands or domains to compare using the data supplied to this workflow. Type: Array. Maximum: 20 items. Default: [].
owned_assetsNoSupplied pages or resources you own that can support prompts or backlink recommendations; this does not edit or publish them. Type: Array. Maximum: 100 items. Default: [].
prompt_countNoMaximum number of prompts to generate in the planned set, not the number of live AI requests. Type: Safe integer. Minimum: 6. Maximum: 50. Default: 20.
product_termsNoProduct names or product-category phrases to incorporate into the planned prompts. Type: Array. Maximum: 40 items. Default: [].
include_citation_checksNoInclude citation-check prompt variants in the plan when true; does not execute those checks. Type: Boolean. Default: true.
include_competitor_checksNoInclude competitor-comparison prompt variants in the plan when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv0.1.5
    • addedInput schema / properties / audience / description
      Added value: +"Intended reader or buyer group in plain language; do not include unnecessary personal data. Type: String. Maximum: 180 characters. Optional; no client default."
    • addedInput schema / properties / cadence / description
      Added value: +"Recommended comparison frequency for the prompt set; does not schedule or execute recurring checks. Type: String. Accepted values: \"weekly\", \"biweekly\", \"monthly\". Default: \"weekly\"."
    • addedInput schema / properties / category / description
      Added value: +"Product or market category used to construct relevant AI-visibility prompts. Type: String. Minimum: 1 characters. Maximum: 160 characters. Required."
    • addedInput schema / properties / competitors / description
      Added value: +"Competing brands or domains to compare using the data supplied to this workflow. Type: Array. Maximum: 20 items. Default: []."
    • addedInput schema / properties / competitors / items / description
      Added value: +"One competing brand or domain name used in the comparison. Type: String. Minimum: 1 characters. Maximum: 160 characters. Required."
    • addedInput schema / properties / include_citation_checks / description
      Added value: +"Include citation-check prompt variants in the plan when true; does not execute those checks. Type: Boolean. Default: true."
    • addedInput schema / properties / include_competitor_checks / description
      Added value: +"Include competitor-comparison prompt variants in the plan when true. Type: Boolean. Default: true."
    • addedInput schema / properties / locale / description
      Added value: +"Human-readable market or locale context for the prompt set, for example United States. Type: String. Minimum: 2 characters. Maximum: 80 characters. Default: \"United States\"."
    • addedInput schema / properties / owned_assets / description
      Added value: +"Supplied pages or resources you own that can support prompts or backlink recommendations; this does not edit or publish them. Type: Array. Maximum: 100 items. Default: []."
    • addedInput schema / properties / owned_assets / items / description
      Added value: +"One page or resource you own, supplied as evidence for the plan. Type: Object. Required."
    • addedInput schema / properties / owned_assets / items / properties / page_type / description
      Added value: +"Page format or classification for this record; select one of the accepted values. Type: String. Accepted values: \"homepage\", \"docs\", \"blog_post\", \"comparison\", \"pricing\", \"product\", \"case_study\", \"tool\", \"other\". Default: \"other\"."
    • addedInput schema / properties / owned_assets / items / properties / title / description
      Added value: +"Title of the supplied page or work item, used as its human-readable label. Type: String. Minimum: 1 characters. Maximum: 180 characters. Required."
    • addedInput schema / properties / owned_assets / items / properties / topics / description
      Added value: +"Relevant topics or themes associated with this target, page or prospect. Type: Array. Maximum: 20 items. Default: []."
    • addedInput schema / properties / owned_assets / items / properties / topics / items / description
      Added value: +"One topic or theme relevant to the supplied entity. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / owned_assets / items / properties / url / description
      Added value: +"Absolute URL of your supplied owned asset to associate with planned prompts; no page fetch is performed. Type: String. Format: absolute URL. Required."
    • addedInput schema / properties / personas / description
      Added value: +"Audience-role labels to vary the planned prompts by buyer context. Type: Array. Maximum: 20 items. Default: []."
    • addedInput schema / properties / personas / items / description
      Added value: +"One audience-role label used to vary prompt context. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / platforms / description
      Added value: +"AI/search platforms to design prompts for; this plans prompts and does not run them on those platforms. Type: Array. Minimum: 1 items. Maximum: 6 items. Default: [\"chatgpt\",\"perplexity\",\"google_ai\"]."
    • addedInput schema / properties / platforms / items / description
      Added value: +"One AI/search platform to design prompts for; no platform request is executed. Type: String. Accepted values: \"chatgpt\", \"perplexity\", \"google_ai\", \"gemini\", \"copilot\", \"claude\". Required."
    • addedInput schema / properties / product_terms / description
      Added value: +"Product names or product-category phrases to incorporate into the planned prompts. Type: Array. Maximum: 40 items. Default: []."
    • addedInput schema / properties / product_terms / items / description
      Added value: +"One product or product-category phrase to include in prompt planning. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
    • addedInput schema / properties / prompt_count / description
      Added value: +"Maximum number of prompts to generate in the planned set, not the number of live AI requests. Type: Safe integer. Minimum: 6. Maximum: 50. Default: 20."
    • addedInput schema / properties / sync / description
      Added value: +"Request a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true."
    • addedInput schema / properties / target / description
      Added value: +"Your target brand, domain or URL used to scope this workflow; supply the entity you want assessed. Type: String. Minimum: 1 characters. Required."
    • addedInput schema / properties / topics / description
      Added value: +"Relevant topics or themes associated with this target, page or prospect. Type: Array. Minimum: 1 items. Maximum: 40 items. Required."
    • addedInput schema / properties / topics / items / description
      Added value: +"One topic or theme relevant to the supplied entity. Type: String. Minimum: 1 characters. Maximum: 120 characters. Required."
  2. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

Given annotations already flag destructiveHint=true and idempotentHint=false, the description goes further by naming the actual mechanism: AgentSEO credits are consumed and a repeated call can produce new charged work. That is precisely the context an agent needs to avoid accidental duplicate spend. It stops short of explaining failure modes or partial results, so not a 5.

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?

Two sentences, front-loaded with the capability and followed by the cost caveat, with no filler. The phrase 'weekly action routing' is slightly opaque jargon, which keeps it from a 5.

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?

For a 15-parameter, credit-consuming tool with no output schema, the description covers purpose and billing risk but says nothing about the shape of the returned prompt set or how pending jobs are handled. Those details live in the schema (sync/poll agentseo_job_status), so an agent relying on the description alone would be under-informed about the result.

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%, so every parameter already carries its own semantics and constraints. The description's enumeration of assets, platforms, competitors, and citations roughly maps to the parameter groups but adds no new meaning, syntax, or defaults 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?

States a specific verb and artifact (build AI visibility prompt sets) and lists the dimensions they are mapped to: owned assets, platforms, competitors, citations, weekly action routing. It is clear what comes out, but it does not name or distinguish itself from any sibling such as agentseo_ai_overview_extract or agentseo_local_visibility_track, which an agent must infer.

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?

The description implies this is a planning/authoring step and warns that repeated calls create new charged work, which shapes usage indirectly, but it never states when to choose this tool over related sibling workflows or what prerequisites (assets, competitor lists) are needed before calling it.

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