Skip to main content
Glama

check_meta

Checks a public URL’s title, meta description, Open Graph, canonical, and hreflang tags to identify metadata issues and guide fixes.

Instructions

检查 title、description、Open Graph、canonical 与 hreflang。

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": {
      "url": "<url>"
    },
    "name": "check_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes完整的 http:// 或 https:// URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about fetching the URL, network access, timeout/failure behavior, or the shape of the results. Only the implicit read-only nature of "check" hints at behavior, and that is inference rather than disclosure.

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

Conciseness3/5

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

One short front-loaded sentence with no filler, but the brevity shades into under-specification rather than efficiency: no structure, no result expectations, and no framing of what a report contains. Nothing in it is wasted, but very little is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that takes a URL and inspects five distinct SEO facets, the definition omits any account of output, per-facet results, or failure modes, and there is no output schema or annotation to compensate. An agent knows roughly what domain it queries but not what it will receive.

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?

There is a single parameter whose schema description already specifies a full http:// or https:// URL (100% coverage). The description adds no meaning beyond that, so the baseline 3 for fully documented parameters applies.

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 names a specific verb (检查/check) and enumerates the exact resources examined: title, description, Open Graph, canonical, and hreflang. That enumeration effectively separates it from siblings like check_robots and check_sitemap, though it never states the distinction explicitly or says what it returns.

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?

There is no guidance on when to use this tool versus check_robots, check_sitemap, or run_audit, and no preconditions (e.g., page must be publicly reachable). The agent is left to infer usage entirely from the tool name and the list of checked fields.

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