Skip to main content
Glama
Sign In

Visibly AI — SEO MCP Server

by io.github.AntonioBlago
OverviewDiscussionsAdmin

seo_guidance

Get SEO best practices on a topic. Topics: title_tags, meta_descriptions, heading_structure, internal_linking, core_web_vitals, eeat, keyword_research, schema_markup, image_optimization, local_seo. Use topic='list' for all. Free - no API key required.

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": {
      "topic": "<topic>"
    },
    "name": "seo_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesSEO topic or 'list' for all topics

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided. Description discloses non-destructive nature and no authentication needed, but doesn't detail return format or result behavior. Adequate for an informational read-only tool.

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

Conciseness5/5

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

Two clear sentences, front-loaded with verb and topic list. No wasted words.

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 simplicity (one required param, no output schema), the description is complete: lists topics, explains usage, notes free and no API key.

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 covers 100% of parameter. Description adds value by enumerating valid topic values and emphasizing 'list' to get all topics, which goes beyond the schema's generic description.

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?

Description clearly states it provides SEO best practices on a topic, lists 10 specific topics, and explains the special 'list' value. Differentiates from siblings like analyze_url_structure and seo_checklist.

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?

Provides explicit usage context: get SEO best practices on a topic, use 'list' for all, free and no API key. Lacks explicit when-not-to-use or alternatives, but context is sufficient for simple tool.

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

All Visibly AI — SEO MCP Server 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