Skip to main content
Glama

Generate web page HTML

web_html_generate
Read-only

Fetch cleaned HTML for a web page URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoWeb page URL to fetch.
linkNoAlias for `url`. Prefer `url`.
pathNoAlias for `url`. Prefer `url`.
trimNoIgnored if this tool does not support it.
limitNoIgnored if this tool does not support it.
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
tweetIdNoAlias for `url`. Prefer `url`.
waitForNoWait for a CSS selector before extraction. Must be prefixed with "css:" (e.g. css:main). JavaScript wait conditions are not supported.
pageSizeNoIgnored if this tool does not support it.
tweetUrlNoAlias for `url`. Prefer `url`.
tweet_idNoAlias for `url`. Prefer `url`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
permalinkNoAlias for `url`. Prefer `url`.
tweet_urlNoAlias for `url`. Prefer `url`.
maxResultsNoIgnored if this tool does not support it.
max_resultsNoIgnored if this tool does not support it.
scanFullPageNoWhen true, scroll the page to load dynamically appended content (infinite scroll). Default false.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / link / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / link / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / path
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `url`. Prefer `url`."
      +}
    • addedInput schema / properties / permalink / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / permalink / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / tweetId / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetId / type
      Removed value: -"string"
    • addedInput schema / properties / tweetUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweetUrl / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_id / type
      Removed value: -"string"
    • addedInput schema / properties / tweet_url / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / tweet_url / type
      Removed value: -"string"
  2. Changed7 schema fields changed
    • addedInput schema / properties / link
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / permalink
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetId
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweetUrl
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_id
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tweet_url
      Added value: +{
      +  "description": "Alias for `url`. Prefer `url`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  3. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url"
      -]New value: +[
      +  "url",
      +  "context",
      +  "llm_model"
      +]
  4. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed2 schema fields changed
    • addedInput schema / properties / scanFullPage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "0",
      +        "1",
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "When true, scroll the page to load dynamically appended content (infinite scroll). Default false."
      +}
    • addedInput schema / properties / waitFor
      Added value: +{
      +  "description": "Wait for a CSS selector before extraction. Must be prefixed with \"css:\" (e.g. css:main). JavaScript wait conditions are not supported.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  7. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations (readOnlyHint=true, openWorldHint=true) already cover the read-only and external-world safety profile, lowering the bar for the description. The description adds that the returned HTML is 'cleaned,' which hints at preprocessing, but it does not disclose auth requirements, JavaScript limitations, rate limits, or what cleaning entails.

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?

The description is a single efficient sentence with the key action front-loaded, and it avoids fluff. However, given the large 19-parameter surface and sibling overlap, a bit more structure (e.g., pointing to url as the preferred parameter or noting the difference from markdown generation) would have earned its place.

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?

There is no output schema, so the description is the only source of return-value information, and 'cleaned HTML' is the sole hint. For a simple fetch tool this is adequate, but it leaves open questions about what cleaning does, whether JS-heavy pages are supported (only waitFor CSS selector is supported per schema), and how to handle the many alias/ignored parameters.

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 coverage is 100%, so every parameter already has a description (e.g., url: 'Web page URL to fetch', aliases marked with 'Prefer url'). The description adds no parameter-specific meaning; it only restates the tool's purpose. The baseline of 3 applies because the schema does the heavy lifting.

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 'Fetch cleaned HTML for a web page URL' states a specific verb (fetch) and resource (cleaned HTML), making the tool's function clear. However, it does not explicitly distinguish it from sibling fetch tools like web_markdown_generate or web_extract_run, and the title 'Generate web page HTML' slightly conflicts with the fetch semantics.

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?

No when-to-use guidance is provided. The one-sentence description does not mention alternatives (web_markdown_generate, web_extract_run, web_screenshot_capture) or conditions for choosing this tool, leaving selection to inference.

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.