Skip to main content
Glama

List Sites

list_sites
Read-onlyIdempotent

List the websites this Zarla account can open: its own, sites shared with it, and every site in a workspace it belongs to. Returns site IDs, names, status (draft/live), and preview URLs. An account with no websites yet returns an empty list plus a message naming create_site as the next step.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds value beyond that: it enumerates the union of site sources returned and documents the empty-list-plus-message behavior, which an agent could not infer from annotations alone. It does not discuss pagination or ordering, which keeps it from 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?

Two sentences, both front-loaded with the useful information: scope first, then return shape, then the edge case. Every clause carries distinct information and nothing is repeated from the annotations.

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?

With no parameters and no output schema, the description must carry the return-value burden itself, and it does: it names the returned fields, the status values, and the empty-result case. Nothing an agent needs to select or call this tool correctly is missing.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. Nothing in the description misdescribes or implies hidden inputs.

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 (list) and resource (websites/sites) plus the exact access scope: owned, shared, and workspace-wide sites. The return fields (IDs, names, draft/live status, preview URLs) make clear this is a summary listing rather than a detail fetch. It stops short of naming get_site as the detail alternative, so the boundary with that sibling is only implied.

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?

The inclusion rule (own + shared + workspace sites) tells the agent what context this tool covers, and the empty-result case is handled explicitly by naming create_site as the next step. There is no explicit when-not guidance or named alternative for retrieving full site details, so it stops at clear context without exclusions.

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.