Skip to main content
Glama

Pagetool

Get a site's preview URL

get_preview_url
Read-onlyIdempotent

Returns the shareable preview URL for a site, plus its expiry. The create tools already return this URL, so call this only when you need it again later. Free, and no account is needed for a draft you created. You can edit or claim this draft for 7 days from creation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_preview_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idNoAlternative lookup by share id, honoured only when it belongs to the caller.
site_keyNoThe site to preview. Defaults to the caller's current draft site when omitted.
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; the description adds real context beyond that: the return includes an expiry, there is no cost, and no account is required for a draft you created. It does not describe failure behavior (unknown site_key, share_id belonging to another caller) or auth needs for non-draft sites, which keeps it below a 5.

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

Conciseness5/5

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

Three short sentences, front-loaded with what is returned, then the routing rule, then the access/lifetime caveats. No filler and nothing repeated from the title.

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?

For a zero-required-parameter read tool with no output schema, the description covers purpose, return contents (URL + expiry), cost/auth and result lifetime, while annotations cover safety. Only edge-case behavior for invalid or foreign lookups is left unstated, a minor gap for this complexity.

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%, so share_id, site_key and draft_token are already fully documented, including the x-pagetool-draft-token header fallback. The description only implicitly touches parameters via 'a draft you created'; baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb and resource ('Returns the shareable preview URL for a site') plus the payload ('plus its expiry'), and explicitly differentiates itself from the create tools that already return the same URL. An agent can identify this as a re-fetch lookup tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use condition: call it only when you need the URL again later, since the create tools already return it. It also names the access condition (free, no account needed for a draft you created) and the 7-day edit/claim window, which frames the useful lifetime of the result.

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