Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

Request a free AI visibility audit

ayrank_request_free_audit

Request a free AY Rank AI visibility audit by submitting your email and website; this creates a lead and notifies the team for follow-up within 24 hours.

Instructions

Use only when the user asks for the free AY Rank AI visibility audit and gives their own email and website. It creates a lead and notifies the AY Rank team; nothing is emailed to you or anyone else. A person from the AY Rank team follows up within 24 hours; this tool does not run the audit itself. 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. Never call it with an email the user did not give you.

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": {
      "email": "<email>",
      "website": "<website>"
    },
    "name": "ayrank_request_free_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe requester's name.
emailYesThe requester's own work email.
notesNoAnything else the team should know.
confirmNoMust be true to send. Leave out to get a dry run.
websiteYesThe site to audit, like https://example.com.
buyer_questionsNoUp to 3 questions a buyer would ask ChatGPT, Perplexity or Google about this market, 200 characters each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds the real behavioral picture: a lead record is created, the team is notified, no email goes to the user, a human follows up within 24 hours, and the audit is not performed by this call. It also discloses the write gate (confirm: true plus AYRANK_MCP_ALLOW_WRITES=1 yields a silent dry run) and a 60-second rate limit — none of which annotations convey.

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?

Front-loaded with the trigger condition, then the side effects, then the gate and rate limit — a sensible order. It is dense with semicolon-chained clauses, so a slightly looser structure would read better, but no sentence is 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, it covers the side effects, the human follow-up, the dry-run path, and the rate limit — enough to call it safely. The only gap is the shape of a successful response (e.g., what the dry-run or confirmation payload contains), which a caller may still want to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema cannot: the email must be the requester's own and user-supplied, and confirm interacts with a server-side env var rather than acting alone. Website and buyer_questions are left to the schema, which is fine given full coverage.

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?

"It creates a lead and notifies the AY Rank team" states a concrete verb and effect, and the explicit clarification "this tool does not run the audit itself" separates it from the sibling analysis tools (crawler access, broken links, title score) that actually produce audit data.

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?

Gives a precise trigger ("Use only when the user asks for the free AY Rank AI visibility audit and gives their own email and website") plus an explicit prohibition ("Never call it with an email the user did not give you"). The gating conditions for actually sending are spelled out, leaving nothing to inference.

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