Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Submit URLs via IndexNow

indexnow_submit
Destructive

Tell every IndexNow engine (Bing, Yandex, Seznam, Naver, Yep, Internet Archive, Amazonbot) that URLs were added or changed, in one call; Google does not take part. Needs no connected account, but the site must host a key file: a text file containing only the key, at https:///.txt or at keyLocation. Without key, the site's mowteng key from indexnow_setup is used. All URLs must be on one host. Cannot be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "indexnow_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe site's own IndexNow key, 8-128 letters, digits or dashes. Omit to use the site's mowteng key (see indexnow_setup).
urlsYesFull URLs on one host, 1-10,000
keyLocationNoFull URL of the key file, when it is not https://<host>/<key>.txt

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses substantial behavior: no connected account required, the mandatory key-file hosting requirement at https://<host>/<key>.txt or keyLocation, the single-host constraint across all URLs, that Google is not covered, and that the action is irreversible. The 'Cannot be undone' statement is consistent with destructiveHint=true and idempotentHint=false, and the no-account note adds context the annotations cannot express.

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

Conciseness4/5

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

It is dense and semicolon-joined, but it is front-loaded with the purpose and engine list and every clause conveys a real constraint (Google exclusion, key file, single host, irreversibility). Minor tightening is possible, but nothing is redundant filler.

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

Completeness4/5

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

For a 3-parameter mutation tool with no output schema, the description covers prerequisites, scope limits, and irreversibility well. The remaining gap is that it never hints at what the call returns (per-engine acceptance, counts, or errors), which matters slightly more because there is no output schema to lean on.

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 all three parameters (key, urls, keyLocation) are already documented in the schema, making 3 the baseline. The description adds only the fallback behavior for an omitted key and restates the one-host constraint that the urls parameter description already carries, so little genuine meaning is added 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 opens with a concrete verb+resource+scope: notifying every IndexNow engine that URLs were added or changed, and it enumerates the engines (Bing, Yandex, Seznam, Naver, Yep, Internet Archive, Amazonbot) while explicitly excluding Google. That exclusion plus the 'one call' framing distinguishes it from the per-engine siblings bing_submit_urls and yandex_submit_urls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the triggering condition clearly ('URLs were added or changed') and covers the key prerequisite path, including the fallback to the mowteng key from indexnow_setup when no key is supplied. What it does not do is explicitly route the agent away from bing_submit_urls/yandex_submit_urls when only one engine matters, so the alternative selection is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources