Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

Add Search Engine to Project

PROJECT_addSearchEngine

Add a search engine to an existing project to track keyword rankings, with support for Google Maps, paid results, and featured snippets.

Instructions

Project Tool: Add a new search engine to a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phoneNoCompany phone number for Google Maps SERPs
site_idYesUnique website ID
lang_codeNoLanguage code
merge_mapNoTake Google Maps SERPs into account. 0 – don’t take into account, 1 – take into account, 2 – take into account and display separately.
region_idNoRegion ID (refer to getSerpLocations)
region_nameNoGeographical name (region / city) in English. Only for Google
paid_resultsNoTrack rankings in Google Ads (1 – yes, 0 – no)
business_nameNoBusiness name for Google Maps SERPs
featured_snippetNoTake Featured snippet into account (1 – take into account, 0 – don’t take into account)
search_engine_idYesSearch engine ID (refer to getAvailableSearchEngines)
Behavior1/5

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

No annotations are present, and the description fails to disclose any behavioral traits (e.g., whether it overwrites existing search engines, required permissions, side effects). The agent has no clue about the tool's behavior beyond the name.

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?

The description is extremely short, omitting critical information. While brevity can be good, here it under-specifies the tool's purpose and usage, making it inefficient for decision-making.

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

Completeness1/5

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

Given the tool has 10 parameters and no output schema or annotations, the description is severely incomplete. It does not explain the process, return values, or interaction with related tools.

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 baseline is 3. The description adds no additional meaning to parameters beyond what the schema already provides.

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 verb 'Add' and resource 'search engine' targeted at 'project'. However, it does not differentiate from sibling tools like PROJECT_updateSearchEngine or PROJECT_deleteSearchEngine, which share similar context.

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 such as PROJECT_updateSearchEngine or PROJECT_deleteSearchEngine. No prerequisites or context 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/TeamDay-AI/se-ranking-mcp'

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