Skip to main content
Glama

sb_site_list

Read-only

Retrieves all Store Builder sites available to the current account, enabling AI agents to identify which sites they can operate.

Instructions

List the sites this account can operate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.103.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.4

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's contribution is limited to the account-scope qualifier ("can operate"), which usefully implies results are permission-filtered. It does not disclose pagination, ordering, or whether "operate" means view-only versus edit rights.

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?

A single seven-word sentence with zero padding and the resource front-loaded after the verb. Brevity is appropriate here, though "operate" is slightly ambiguous and one more clause on scope would still have been cheap.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only listing tool this is close to sufficient, but with no output schema the agent gets no sense of what a site record contains or whether results are truncated. A brief note on return shape or pagination would close the remaining gap.

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?

Zero parameters, so there is no parameter semantics to explain; baseline of 4 applies. The empty schema with additionalProperties=false is consistent with the description's claim of a no-argument listing call.

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 ("sites"), which separates it from the page/media-focused list siblings (sb_page_list, sb_media_list). The scope note "this account can operate" adds a permission qualifier, though it never names an alternative tool explicitly.

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

Usage Guidelines2/5

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

No explicit guidance on when to call this versus siblings such as sb_page_list, sb_import_site, or sb_catalog_search. The only hint of applicable context is the phrase "this account can operate," leaving the agent to infer that this is the entry point for enumerating accessible sites.

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