Skip to main content
Glama

Read a web page as a reference

playground_web_page_read

Fetch a public HTTPS page (product page, article, landing page, or social post) with private-network, size and type checks, and return its title, description, card, JSON-LD product data, headings, main text and images with source URL, retrieval time and content hash. Social links and script-rendered pages are metadata_only. JavaScript is not run and embedded video/audio is never watched. With placeOnCanvas (needs canvas:edit and expectedRevision) it also adds a source card and up to three product images to the canvas.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS URL of the source to inspect or import; use the original source link.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
placeOnCanvasNoWhether to add the fetched page and usable reference images to the canvas; requires edit access and a current revision.
expectedRevisionNoCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
placedNo
referenceYesFetched web reference, including coverage, extracted content and provenance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint=true, destructiveHint=false, readOnlyHint=false), the description discloses the real behavioral traits: private-network/size/type checks, degraded metadata_only output for social and JS-rendered pages, no JavaScript execution, no media playback, and that placeOnCanvas is a mutation requiring canvas:edit and expectedRevision. The readOnlyHint=false is consistent, since the canvas write path is spelled out rather than contradicted.

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 verb and resource are front-loaded in the first clause, and each sentence carries distinct information (capabilities, limitations, canvas mutation). The return-field enumeration is somewhat list-heavy and partially redundant with the existing output schema, costing a bit of density.

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?

For a four-parameter, open-world fetch tool with an output schema, the definition covers everything an agent needs: what is fetched, what comes back, what degrades, what is never executed, and the permissions/revision prerequisites for the mutating branch. Nothing material is left to inference.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: placeOnCanvas is only meaningful together with canvas:edit access and expectedRevision, and it caps images at three. That relational constraint is genuine added value; URL and projectId semantics are left entirely to the schema.

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 opens with a specific verb+resource ('Fetch a public HTTPS page') and enumerates the accepted page types (product page, article, landing page, social post), plus what it returns. It is clear what the tool does, but it never names or contrasts a sibling (e.g. external_link_inspect or asset_import), so an agent must infer which fetch-like tool to pick.

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?

Usage context is well established: public HTTPS only, implicit private-network/size/type gating, and the placeOnCanvas variant described as an add-on mode. Exclusions are stated behaviorally (social links and script-rendered pages return metadata_only, JS is not run, video/audio is never watched). What is missing is explicit routing against alternative tools for the same goal.

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.