Skip to main content
Glama

mcp-server

by com.abbyseo

Purchase the Full SEO Remediation Guide

purchase_report

Start a purchase of the full paid SEO Remediation Guide for a COMPLETE scan ($8.99). Returns a Stripe checkout_url — payment CANNOT be collected through this tool. AUTONOMOUS FLOW: after calling this, do NOT stop and wait for a new user instruction. (1) Show the user checkout_url and ask them to complete payment in their browser. (2) Then poll get_purchase_status with the same scan_id about every 15 seconds: while paid is false the user hasn't finished — keep waiting (poll for up to a few minutes). (3) Once paid and runbook_ready are both true, call get_remediation_plan once, save the returned markdown to the file it names, and begin the remediation automatically — no further prompting needed. If this call returns already_purchased=true, skip the wait and go straight to get_remediation_plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scan_idYesScan ID from submit_scan. The scan must be 'complete'.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations indicate openWorldHint=true (side effects) and non-idempotent, which the description confirms by detailing that it initiates a purchase and returns a checkout URL. It adds critical context: payment must be done externally, the tool does not collect payment, and the autonomous flow for polling and follow-up. No contradictions with annotations.

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 purpose and proceeds logically to detailed instructions. While it is relatively long, every sentence adds value, and the numbered flow improves clarity. Minor conciseness improvement could be achieved by trimming redundant phrasing, but overall well-structured.

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

Completeness5/5

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

Given the tool's complexity (purchase initiation, external payment, polling, conditional behavior), the description fully covers all necessary information. No output schema exists, but the description explains return values (checkout_url and already_purchased flag) and the entire workflow.

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 coverage is 100% with a clear description for scan_id. The tool description does not add further parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 ('Start a purchase'), specific resource ('the full paid SEO Remediation Guide'), price ($8.99), and context ('for a COMPLETE scan'). It distinguishes from sibling tools like get_purchase_status and get_remediation_plan by focusing on initiating payment.

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 explains when to call ('scan must be complete'), that payment cannot be collected through the tool, and provides a numbered autonomous flow with polling logic, condition handling (already_purchased), and next steps. No ambiguity about when to use this tool versus alternatives.

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

All mcp-server 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.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: starting scans, polling status, retrieving results, looking up old scans, checking purchase status, purchasing, getting remediation plans, and server documentation. No ambiguity between tools.

Naming Consistency4/5

Seven tools follow a consistent verb_noun pattern (e.g., get_scan_results, purchase_report). The outlier 'how_to_use' deviates slightly from the pattern. Overall naming is coherent and readable.

Tool Count5/5

Eight tools cover the full SEO scan workflow without being excessive. Each tool serves a necessary step, from submission to remediation, so the count is well-scoped for the server's purpose.

Completeness4/5

The tool set covers the core workflow: scan submission, status polling, results retrieval, purchase, purchase status, and remediation plan retrieval. A minor gap is the lack of a tool for user account management or scan history beyond email lookup, but these are not essential for the primary use case.

Resources