Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Domain Ads by Domain

domainAdsByDomain

Retrieve paid ad data for a specific domain by country code and optional date range. Identify which domains are advertising on the target domain.

Instructions

Fetch domain ads by domain (v1/domain/ads)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesAlpha-2 country code of the regional keyword database.
domainYesThe specific domain for which to retrieve its paid ad data.
fromNoThe starting year and month for the data retrieval period, formatted as “YYYY-MM” (e.g., “2017-01”).
toNoThe ending year and month for the data retrieval period, formatted as “YYYY-MM”.
pageNoFor paginated results, specifies the page number of domains advertising on this keyword to retrieve.
limitNoThe maximum number of domains (advertising on the keyword) to return per page.
Behavior2/5

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

No annotations provided, so description bears full burden. Only states what the tool does, but discloses no behavioral traits such as pagination behavior, rate limits, or data returned.

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

Conciseness2/5

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

Extremely short (one sentence) but under-specified; includes unnecessary API version info while omitting key context. Not efficiently informative.

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?

With 6 parameters, no output schema, and no annotations, the description is incomplete; lacks explanation of pagination, return format, or how to interpret results.

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%; description adds no additional meaning beyond schema descriptions, so baseline of 3 is appropriate.

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?

Description states action ('Fetch') and resource ('domain ads'), but merely repeats the tool name and doesn't differentiate from sibling tools like 'domainAdsByKeyword'.

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 versus alternatives (e.g., domainAdsByKeyword), no context on prerequisites or exclusions.

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