Skip to main content
Glama

page_metadata

Extract titles, meta/OG/Twitter tags, headings, forms, scripts, and IDs from a URL to profile targets and uncover analytics IDs, frameworks, and hidden endpoints.

Instructions

Extract page metadata: title, meta/OG/Twitter tags, headings, forms, scripts, IDs.

Useful for profiling a target and spotting analytics IDs, frameworks and hidden endpoints referenced in the page.

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": "page_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/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. 'Extract' implies a read-only fetch, and the enumerated fields hint at the return shape, but nothing is said about whether the page is fetched live or from cache, whether JavaScript is executed, redirect handling, auth/cookie requirements, or rate limits. Adequate but thin for a zero-annotation tool.

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?

Two sentences, front-loaded with the concrete output list, followed by the motivating use case. No filler or redundancy. Slightly dense field list, but every item earns its place by defining the return shape.

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

Completeness3/5

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

With no annotations and no output schema, the description's field enumeration partly substitutes for a return-value spec, which is helpful. Still missing are the fetch semantics (live vs cached, JS rendering, structured vs raw output) that an agent needs to pick this over browser_extract or browser_crawl. Adequate but with clear gaps.

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 required 'url' parameter with 0% schema description coverage, and the description never mentions it. It does not clarify accepted URL forms (scheme required?), redirect or non-HTML handling, or whether subresources are fetched. The field enumeration adds some value but not about the parameter itself.

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?

States a concrete verb ('Extract') plus resource ('page metadata') and enumerates the specific fields returned (title, meta/OG/Twitter tags, headings, forms, scripts, IDs). An agent knows exactly what it will get back. It does not explicitly differentiate itself from near-neighbours like browser_extract or browser_crawl, which keeps it short of a 5.

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 second sentence gives a use context ('profiling a target and spotting analytics IDs, frameworks and hidden endpoints'), which implies reconnaissance-phase usage. However, there is no explicit when-not guidance and no named alternative for overlapping tasks such as full-page extraction or crawling, so the agent has to infer routing.

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