Skip to main content
Glama

project_seo_check

Read-onlyIdempotent

Inspect deployed SEO metadata from the active release's homepage HTML, robots.txt and sitemap.xml artifacts. Returns release identity, automatic fallback versus app-supplied provenance, metadata issues and advisory suggestions. This does not fetch the public site, execute JavaScript, crawl routes, edit source or verify indexing/ranking. Public HTTP/function responses and client-route coverage remain unobserved.

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": {
      "project_id": "<project_id>"
    },
    "name": "project_seo_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID, subdomain or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so the safety profile is covered. The description goes further by disclosing what the result contains (release identity, fallback vs. app-supplied provenance, issues, advisory suggestions) and, importantly, what remains unobserved (public HTTP/function responses, client-route coverage) — a genuine coverage caveat. It does not mention preconditions such as whether an active release must exist.

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?

Three tight sentences, front-loaded with purpose before scope and exclusions; no filler. Slightly dense, but each sentence contributes scope or limitation information.

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?

With no output schema, the description correctly spends space on what is returned, and the explicit unobserved-areas note prevents over-trusting the results. The one gap is deployment preconditions — it references the 'active release' but not what happens when none exists.

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 description coverage is 100% for the single required `project_id`, and the description adds no further semantics such as accepted formats or behavior for unknown slugs. Baseline 3 applies when the schema already carries the parameter meaning.

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 opens with a specific verb and resource pair: inspect deployed SEO metadata from the active release's homepage HTML, robots.txt and sitemap.xml. It then draws hard boundaries ('does not fetch the public site, execute JavaScript, crawl routes, edit source or verify indexing/ranking'), which clearly separates it from a crawler or domain/site checker without needing to name a sibling.

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?

The exclusion list gives strong negative guidance — an agent knows not to use this for live HTTP checks, JS-rendered metadata, route crawling, or ranking verification. It stops short of naming an alternative tool for those cases, so routing remains partly inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources