Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

AI Search Discover Brand

DATA_getAiDiscoverBrand

Identify the brand name from a domain, subdomain, or URL. Use the returned brand for other AI search queries.

Instructions

Data Tool: Identifies and returns the brand name associated with a given target domain, subdomain, or URL. Useful for determining what brand name to use in other AI search queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoThe scope of the analysis. Can be base_domain (aggregate by registrable domain, includes all subdomains), domain (exact host only, no subdomain aggregation), or url (exact URL including path and query).domain
sourceYesAlpha-2 country code for the regional prompt database (e.g., us for United States results).
targetYesThe target to analyze. Can be a root domain, subdomain, or a specific URL.
Behavior3/5

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

With no annotations provided, the description must convey behavioral traits. It implies a read-only operation by saying 'Identifies and returns,' which is appropriate. However, it does not explicitly state that no changes are made, nor does it disclose potential dependencies or limits, leaving some uncertainty.

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 only two sentences, front-loading the core action and resource. Every word contributes meaning without redundancy, making it highly concise and well-structured.

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?

Given the tool's simplicity and full schema coverage, the description is mostly adequate. However, it does not specify the output format (e.g., returns a string), which is a minor gap. It mentions usefulness for AI search queries, which helps contextual completeness.

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 covers all three parameters with descriptions, resulting in high schema coverage. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline but does not enhance understanding.

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 tool's purpose: 'Identifies and returns the brand name associated with a given target domain, subdomain, or URL.' It uses a specific verb ('Identifies and returns') and resource ('brand name'). However, it does not explicitly differentiate from sibling tools like DATA_getAiPromptsByBrand, though the distinction is implicit.

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 notes the tool is 'Useful for determining what brand name to use in other AI search queries,' providing a context for use. However, it lacks explicit guidance on when not to use it or mention of alternatives, such as directly using domain knowledge or other tools.

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