Skip to main content
Glama

List sites

list_sites
Read-only

The owner's Stick sites: id, name, status (unpublished, published or unpublished-changes), address and three dashboard links. The address shows the site only once it is published. editorUrl opens the page editor and nothing else: it has no stats or leads. analyticsUrl is the site's Analytics (visits, clicks, referrers; no export) and audienceUrl its Audience (people who filled in a form or bought a Digital Product, one row per email, with a CSV export). No tool reads these, and Stick has no orders page: send the owner to those links instead of guessing where to look.

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.3/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, non-open-world behavior, and the description adds real substance on top: the address is only populated once a site is published, editorUrl covers only the page editor (no stats or leads), analyticsUrl has no export while audienceUrl offers a CSV export. The one gap is that it doesn't say what happens with zero sites or whether the list is paginated or ordered.

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?

Content is front-loaded: the resource and fields come first, then field-level caveats, then the routing advice. It is dense and runs long in the middle section about the three dashboard links, but given there is no output schema each of those clauses carries information the agent cannot get elsewhere.

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 output schema and no parameters, the description carries the full burden of explaining return values, and it does so field by field, including status enum values and the published-only address caveat. Nothing an agent needs in order to call this tool and interpret its result 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 nothing for the description to disambiguate and the baseline of 4 applies. The space is instead spent explaining the shape of each returned field, which is useful but belongs to a different dimension.

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 opening sentence names the resource precisely ('The owner's Stick sites') and enumerates the returned fields (id, name, status, address, three dashboard links), so an agent knows this is a list-all-sites read. It never names the sibling get_site to contrast single-site retrieval with this plural listing, so sibling differentiation is only implicit through the plural phrasing.

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?

It gives explicit routing rules beyond simple 'use this to list': 'No tool reads these... send the owner to those links instead of guessing where to look', plus the statement that Stick has no orders page. That tells the agent both what to do with the result and what not to attempt elsewhere, which is exactly the when/when-not guidance the dimension asks for.

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