Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

AI Search: Get Prompts by Target (SE Ranking)

aiSearchPromptsByTarget

Retrieve prompts from AI search engines that mention a specific domain or URL, enabling analysis of brand visibility and context in LLM responses.

Instructions

Fetch the list of prompts (queries) that refer to or mention a given target (domain/URL) in the AI Search context. Corresponds to SE Ranking’s “Get Prompts by Target” API section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYesType of LLM engine (e.g. 'chatgpt', 'perplexity', 'ai-mode', etc.).
targetYesThe target to retrieve prompts for (domain, host, or URL).
sourceYesAlpha-2 country code of the regional prompt database (e.g. 'US').
scopeNoScope of analysis: base_domain (the root domain only), domain (the domain including all subdomains), or url (an exact URL).base_domain
sortNoThe field to sort the results by. Options: volume, type, snippet_length.volume
sort_orderNoSort order ('asc' for ascending, 'desc' for descending). Default is 'desc'.desc
limitNoMaximum number of prompts to return.
offsetNoOffset for pagination (starting index).
filter[volume][from]NoSpecifies the minimum volume of searches to be included in the results.
filter[volume][to]NoSpecifies the maximum volume of searches to be included in the results.
filter[keyword_count][from]NoSpecifies the minimum number of words in prompts.
filter[keyword_count][to]NoSpecifies the maximum number of words in prompts.
filter[characters_count][from]NoSpecifies the minimum prompt length in characters.
filter[characters_count][to]NoSpecifies the maximum prompt length in characters.
filter[multi_keyword_included]NoA URL-encoded JSON string specifying keywords that must be present in the prompt. For example: filter[multi_keyword_included]=[[{"type":"contains","value":"seo"},{"type":"contains","value":"tools"}],[{"type":"contains","value":"backlinks"}]]
filter[multi_keyword_excluded]NoA URL-encoded JSON string specifying keywords that must NOT be present in the prompt. For example: filter[multi_keyword_excluded]=[[{"type":"contains","value":"seo"},{"type":"contains","value":"tools"}],[{"type":"contains","value":"backlinks"}]]
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, authentication requirements, or pagination behavior (though limit/offset parameters exist). The description is minimal and does not compensate for missing annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no fluff. It front-loads the purpose and references the API section concisely.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 16 parameters and no output schema, the description fails to mention return values, error handling, or output format. It is insufficient for a complex tool with rich filtering capabilities.

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?

The input schema has 100% description coverage for all 16 parameters, so the description adds no additional meaning. Baseline score of 3 is appropriate as the schema already provides semantic clarity.

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 the tool fetches a list of prompts that mention a given target (domain/URL). It uses specific verbs ('Fetch') and resource ('prompts that refer to or mention a given target'), and distinguishes from sibling tools like aiSearchOverview and aiSearchPromptsByBrand.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., aiSearchPromptsByBrand). Sibling tools are listed but no explicit when-to-use or when-not-to-use instructions are provided.

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/Teake1404/seo-data-api-mcp-server'

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