Skip to main content
Glama
AntonioBlago

VisiblyAI MCP Server

by AntonioBlago

seo_guidance

Get SEO best practices on topics like title tags, meta descriptions, and keyword research. Use topic='list' to see all available topics.

Instructions

Get SEO best practices on a topic. Use topic='list' to see all topics.

Topics: title_tags, meta_descriptions, heading_structure, internal_linking, core_web_vitals, eeat, keyword_research, schema_markup, image_optimization, local_seo.

Free tool - no API key or credits required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist. The description mentions it's free and requires no API key, which is helpful, but does not disclose if the tool has any side effects, rate limits, or the nature of returned data. Output schema exists but is not described.

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 extremely concise, front-loads the core purpose, and lists topics efficiently. Every sentence is meaningful.

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?

Given the tool's simplicity (one parameter, output schema exists), the description adequately covers purpose, valid inputs, and cost. It could mention return format but output schema compensates.

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?

The input schema only specifies a string with no enum values, but the description enriches semantics by listing all valid topics (e.g., title_tags, meta_descriptions), providing significant added value beyond the schema.

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 'Get SEO best practices on a topic' with a specific verb and resource. It does not explicitly differentiate from siblings, but the topic enumeration adds clarity.

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

Usage Guidelines3/5

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

The description provides a usage tip (topic='list') and states it's free, but lacks explicit guidance on when to use this tool versus sibling tools like seo_checklist or seo_workflow.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AntonioBlago/visiblyai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server