Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

Update Search Engine

PROJECT_updateSearchEngine

Update an existing search engine entry in your project—adjust language, region, Google Maps integration, and featured snippet settings.

Instructions

Project Tool: Update an existing search engine in 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
site_engine_idYesUnique search engine ID within the project (not global ID)
featured_snippetNoTake Featured snippet into account (1 – take into account, 0 – don’t take into account)
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only states the basic action without mentioning side effects, permissions, or error conditions.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks depth for a tool with 10 parameters. It is front-loaded but too brief.

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 10 parameters, no output schema, and no annotations, the description fails to provide sufficient context about return values, constraints, or expected behavior.

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 beyond the schema.

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 verb 'Update' and the resource 'existing search engine in a project', distinguishing it from sibling tools like add and delete.

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 is provided on when to use this tool versus alternatives like PROJECT_addSearchEngine or PROJECT_deleteSearchEngine. No context on prerequisites or usage constraints.

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