Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Submit URLs to IndexNow

ayrank_indexnow_submit

Submit up to 100 URLs from a host you control to IndexNow after the key file check passes, sharing changed pages with participating search engines; requires confirm:true and writes enabled.

Instructions

Use to submit up to 100 URLs on a host you control to IndexNow (step 2, after ayrank_indexnow_key_check passes). The AY Rank API checks the URLs and re-checks the key file, then posts them to api.indexnow.org, which shares them with the search engines that take part in IndexNow. Gated: without confirm: true and AYRANK_MCP_ALLOW_WRITES=1 on the server it returns a dry run and sends nothing. At most once per 60 seconds. Not for sites you do not control.

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": {
      "host": "<host>",
      "key": "<key>",
      "urlList": "<urlList>"
    },
    "name": "ayrank_indexnow_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe IndexNow key whose key file is live on the host.
hostYesThe host, like www.example.com.
confirmNoMust be true to send. Leave out to get a dry run.
urlListYesURLs on the host, at most 100.
keyLocationNoThe key file URL when it is not at the root, on the same host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the two-part write gate (confirm: true plus AYRANK_MCP_ALLOW_WRITES=1), the resulting dry-run behavior when ungated, the 60-second rate limit, and the downstream propagation to api.indexnow.org. The external side effect is consistent with openWorldHint=true and the sending behavior is consistent with readOnlyHint=false.

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?

Purpose and prerequisite are front-loaded in the first sentence, followed by mechanics and gating. Slightly dense at four clauses, but each carries operational information (gating, rate limit, scope) rather than 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 mutation tool with no output schema and five fully documented parameters, the description covers prerequisites, gating, throttling, and scope. The only gap is what a successful response looks like, which is minor given the dry-run explanation.

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 every parameter including confirm and keyLocation is already documented in the schema. The description reinforces the confirm gating and notes the key file is re-checked, but adds little parameter-level meaning beyond what the schema states; baseline 3 applies.

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?

States a specific verb and resource ('submit up to 100 URLs on a host you control to IndexNow') plus scope limits, so an agent can distinguish it from sibling checks like ayrank_indexnow_key_check without opening either schema.

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

Usage Guidelines5/5

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

Explicitly positions the tool as 'step 2, after ayrank_indexnow_key_check passes' and adds a clear exclusion, 'Not for sites you do not control.' Both the ordering prerequisite and the negative case are named directly.

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