Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Add site

add_site

Add a site to the account or reuse the existing domain. Up to 1,000 sites per account. This creates no subscription or payment. An account holds up to 1,000 sites (409 site_limit). Adding a site creates no subscription or payment. The existing guest audit workspace stays separate. Returns: { site{id,host,url,created_at,_links} } Example: await fetch("$ORIGIN/api/sites", {method:"POST", headers:{"Content-Type":"application/json", "X-CSRF-Token":csrf}, body:JSON.stringify({url:"https://example.com/"})}); Errors: 400: invalid_site_url or invalid_body; 401: account_required or session_ended; 403: account_required or invalid_csrf; 404: site_not_found; 409: site_limit; 503: sites_unavailable

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP(S) URL, without credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description goes further by disclosing the per-account cap, the absence of billing side effects, the return payload shape, and the full error surface (400/401/403/404/409/503). The only mild tension is 'reuse the existing domain' versus idempotentHint=false, but that is ambiguous rather than contradictory.

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

Conciseness2/5

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

The lead sentence is well front-loaded, but the text repeats itself twice ('Up to 1,000 sites per account' and 'This creates no subscription or payment' both appear twice), and the raw fetch snippet inflates length without adding much beyond the schema.

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 single-parameter mutation with no output schema, the description covers the return shape, error taxonomy, limits, and side-effect profile, which is enough for an agent to call it correctly. Only the sibling routing and any idempotent-reuse semantics are left unclear.

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% and the single url parameter is already documented as a public HTTP(S) URL without credentials, so the schema does the heavy lifting. The embedded fetch example does reinforce the expected JSON body format, but no additional validation rules or normalization behavior is explained.

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 specific verb+resource ('Add a site to the account') and clarifies the dual behavior: creating a new site or reusing an existing domain. It also explicitly separates it from the guest audit workspace, which helps an agent distinguish related operations, though it never names list_sites/get_site as alternatives.

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?

Provides useful operating context (1,000 sites per account, no subscription or payment created, guest audit workspace unaffected) and enumerates the error codes including site_limit, but gives no explicit 'use this instead of X when Y' routing against siblings like list_sites or get_site.

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

All pageaudit toolsInspect
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