Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

AI Search: Get Prompts by Target (SE Ranking)

DATA_getAiPromptsByTarget

Retrieve AI search prompts mentioning a target domain or URL. Analyze which queries trigger AI-generated responses to understand your visibility in AI search results.

Instructions

Data Tool: Retrieves a list of prompts (queries) that mention the specified target in AI search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoThe field to sort the results by. Options: volume, type, snippet_length.volume
limitNoMaximum number of prompts to return.
scopeNoThe scope of the analysis. Can be base_domain (domain and all subdomains), domain (specific host), or url (exact URL).base_domain
engineYesType of LLM engine (e.g. 'chatgpt', 'perplexity', 'ai-mode', etc.).
offsetNoOffset for pagination (starting index).
sourceYesAlpha-2 country code of the regional prompt database (e.g. 'US').
targetYesThe target to retrieve prompts for (domain, host, or URL).
sort_orderNoSort order ('asc' for ascending, 'desc' for descending). Default is 'desc'.desc
filter_volume_toNoSpecifies the maximum volume of searches to be included in the results.
filter_volume_fromNoSpecifies the minimum volume of searches to be included in the results.
filter_keyword_count_toNoSpecifies the maximum number of words in prompts.
filter_keyword_count_fromNoSpecifies the minimum number of words in prompts.
filter_characters_count_toNoSpecifies the maximum prompt length in characters.
filter_characters_count_fromNoSpecifies the minimum prompt length in characters.
filter_multi_keyword_excludedNoA 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"}]]
filter_multi_keyword_includedNoA 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"}]]
Behavior2/5

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

No annotations provided, so the description carries full burden. It states the tool retrieves data (implying read-only) but does not disclose any behavioral traits such as authentication requirements, rate limits, or what happens if the target is not found.

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 a single sentence of 18 words, efficiently conveying the core purpose with no extraneous information. It is front-loaded and well-structured.

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 the tool having 16 parameters, no output schema, and complex filtering/sorting features, the description provides minimal context. It does not mention pagination, volume, filtering capabilities, or the nature of the returned data, leaving the agent dependent solely on the schema.

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%, and the schema already provides detailed descriptions for all 16 parameters. The description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

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?

The description clearly states the action ('Retrieves a list of prompts') and the resource ('that mention the specified target in AI search results'). It distinguishes from the sibling 'DATA_getAiPromptsByBrand' by using 'target' instead of 'brand', though it could explicitly call out the difference.

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 like 'DATA_getAiPromptsByBrand' or 'DATA_getAiOverview'. No mention of prerequisites or context for the tool.

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/TeamDay-AI/se-ranking-mcp'

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