Skip to main content
Glama
atomno-mcp

atomno-mcp-seo-audit

Official
by atomno-mcp
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

build_meta

Generate meta tags including title, description, canonical, Open Graph, and Twitter Card. Validates title (50-60 chars) and description (120-160 chars) lengths for SEO.

Instructions

Сгенерировать -мета-теги (title, description, canonical, Open Graph, Twitter Card) и проверить длины title (50–60) и description (120–160). Возвращает готовый блок тегов.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoЯзык сообщений: 'ru' или 'en'.ru
fieldsYestitle, description, url (canonical), image (og 1200×630), site_name, type, twitter_card, locale.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

With no annotations, the description covers the generative and validation behavior, but does not mention side effects, prerequisites, or error handling.

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 concise sentences with all essential information, no superfluous content.

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?

The description is complete for a simple generation tool with output schema; it explains purpose, validation, and output.

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?

Adds value beyond the schema by specifying length checks (title 50–60, description 120–160) and that it returns a ready block; schema already covers field keys and lang options.

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 tool generates <head> meta tags (title, description, canonical, Open Graph, Twitter Card) and validates lengths, distinguishing it from sibling tools like build_jsonld or audit_site.

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?

No explicit when or when-not guidance is provided; usage context is implied but not delineated against alternatives.

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/atomno-mcp/mcp-seo-audit'

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