PageHub

Select site

select_site

Read-onlyIdempotent

Set the active site for this session and clear any active template. Returns the site's settings and its previewUrl. The hosted server doesn't keep it between calls — still pass id on every call.

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": {
      "id": "<id>"
    },
    "name": "select_site"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Site id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description adds meaningful behavioral context: it clears any active template, returns the site's settings and previewUrl, and explains that the hosted server does not retain the selection between calls. This is valuable context not captured by readOnlyHint or idempotentHint.

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?

The description is three tightly written sentences with no wasted text. The core action is front-loaded, and the operational caveats follow immediately.

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?

Although there is no output schema, the description explains what is returned: the site's settings and previewUrl. It also covers the session and non-persistence behavior, leaving no major gaps for an agent invoking this tool.

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. The description adds a useful usage nuance by emphasizing that `id` must still be passed on every call despite the session not persisting it, which goes slightly beyond the schema's 'Site id.'

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?

The description states a specific verb and resource: 'Set the active site for this session.' It also clarifies scope by saying it clears the active template, which distinguishes it from sibling tools like update_site or list_sites.

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?

It clearly implies when to use this tool: to make a site active for the current session. It also warns that the hosted server does not persist the selection, so `id` must be passed on every call. It does not name alternatives, but no obvious sibling alternative exists for this session-selection purpose.

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

All PageHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?