Skip to main content
Glama
Sign In
VisiblyAI MCP Server

VisiblyAI MCP Server

by AntonioBlago
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

seo_checklist

Generate an SEO checklist for types: general, blog, ecommerce, discover, backlink, or all. Choose English or German to verify actionable items.

Instructions

Get an SEO checklist. Types: general, blog, ecommerce, discover, backlink, all.

Returns actionable checklists with specific items to verify. Available in English (en) and German (de).

Free tool - no API key or credits required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoen
checklist_typeNogeneral

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description provides transparency about cost ('Free tool - no API key or credits required') and return type ('actionable checklists'). However, it doesn't explicitly state read-only behavior or potential side effects.

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?

The description is concise with three sentences, front-loading the purpose. Every sentence adds value (types, return, language, free aspect), with no wasted words.

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 simple retrieval tool, the description covers purpose, parameters, return format, and availability. It lacks details on limitations (rate limits, max results), but given the output schema exists and the tool is free, it's fairly complete.

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 0%, but the description partially compensates by listing checklist type values (general, blog, etc.) and language options (en, de). However, it does not explain each type's purpose or confirm exact allowed values, leaving ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns an SEO checklist and lists available types (general, blog, ecommerce, etc.). It distinguishes the tool from siblings like seo_agent or seo_guidance by focusing on checklists, but does not explicitly contrast them.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or compare with other SEO tools like seo_guidance or seo_workflow.

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

Deploy Server

Other Tools