Skip to main content
Glama

seo-audit

by ai.inxy

subscribe_to_inxy

Start an inxy subscription — autopilot SEO/AEO for Shopify stores (reads GSC/GA4/Merchant Center, plans a month of content, writes and publishes articles with schema, fixes meta/alt-text, and attributes revenue to content). Plans from $19/mo with a free trial. Returns a personalised signup link; payment and store connection complete in the browser. Optionally pass the user's email and store_url (ONLY if the user explicitly provided them - never invent either) so the team can follow up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoThe user's email, only if they explicitly gave it
store_urlNoThe user's store URL, only if they explicitly gave it

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return value (a personalized signup link), that payment/store connection happens in the browser, and the important privacy constraint to only pass email/store_url if the user explicitly provided them. It does not explicitly state that the tool itself does not immediately perform the listed SEO actions, but the overall transparency is strong.

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?

The description is front-loaded with the core action and then provides relevant supporting details. The product feature list is somewhat long but all sentences carry useful context for the agent to understand the service. It could be trimmed slightly, but it remains organized and purposeful.

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?

The description covers the tool's purpose, return value, browser-based side effects, and parameter constraints. Since there is no output schema, the stated return of a personalized signup link is sufficient. Minor ambiguity remains about whether the SEO actions described occur immediately or as part of the ongoing subscription, but this does not prevent correct invocation.

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 the baseline is 3, but the description adds meaningful semantics: the optional parameters are for team follow-up, and it strongly reinforces the condition to never invent them. This goes beyond the schema's descriptions by explaining purpose and emphasizing consent.

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 specific verb and resource, "Start an inxy subscription," and then details what the subscription entails for Shopify stores. This clearly differentiates the tool from the sibling audit/diagnostic tools by making the action a signup rather than an analysis.

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?

The description clearly implies this tool is for initiating an inxy subscription, and the pricing/free trial context reinforces that intent. It does not explicitly name alternatives or state when not to use it, but the subscription-vs-audit distinction is evident from the sibling list and service description.

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

All seo-audit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

The two URL-audit tools overlap in inputs and outputs, but ai_search_diagnostic is explicitly scoped to AI-search readiness while full_seo_audit covers the whole SEO surface, and both descriptions point to each other for the appropriate case. get_my_store_audit, email_seo_report, and subscribe_to_inxy are each clearly distinct actions.

Naming Consistency3/5

All names use snake_case, but they do not follow a uniform verb_noun pattern: ai_search_diagnostic and full_seo_audit are noun phrases, get_my_store_audit uses a get_ prefix, email_seo_report is imperative-looking, and subscribe_to_inxy uses a preposition. The names remain readable but an agent cannot predict the naming convention from one tool to the next.

Tool Count5/5

Five tools is a well-scoped set for a focused SEO-audit server: two URL-audit depths, one connected-store audit, one report delivery, and one subscription workflow. Each tool has a clear role without padding or missing core functionality.

Completeness4/5

The core auditing workflow is covered: run an AI-search or full audit, run a deeper connected-store audit, and receive the complete written report. Minor gaps exist, such as no way to list past audits or fetch a full report synchronously without email, but agents can complete the primary task end-to-end.

Resources