Skip to main content
Glama
Drop-to-run

drop2run-mcp

Official
by Drop-to-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List sites

list_sites
Read-only

Retrieve a list of sites on your account to select a destination for publishing static files.

Instructions

Lists the sites on this account, so a publish can go to one of them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sitesYesThe account's sites, newest first — every one unless `total` is larger.
totalYesHow many sites the account holds. Larger than `sites` only past 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.4
    • changedOutput schema / properties / sites / description
      Previous value: -"Every site on this account."New value: +"The account's sites, newest first — every one unless `total` is larger."
    • addedOutput schema / properties / total
      Added value: +{
+  "description": "How many sites the account holds. Larger than `sites` only past 100.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "sites"
-]New value: +[
+  "sites",
+  "total"
+]
  2. Changed1 schema field changedv0.2.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "sites": {
+      "description": "Every site on this account.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "name": {
+            "description": "What it is called, or null when it has no name.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "siteId": {
+            "description": "Identifier of the site.",
+            "type": "string"
+          },
+          "subdomain": {
+            "description": "Its subdomain, which is what `site` accepts.",
+            "type": "string"
+          },
+          "url": {
+            "description": "Its live URL.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "siteId",
+          "subdomain",
+          "url",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sites"
+  ],
+  "type": "object"
+}
  3. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the account scoping and the downstream purpose (targets for publish), but says nothing about pagination, ordering, or result size for a list operation.

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?

A single short sentence with zero filler, front-loading the action and resource and appending only the one useful piece of context. Every word earns its place.

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?

With an output schema present, return values need no explanation, and the zero-parameter, read-only nature means little else is required. Minor gaps remain around result volume/pagination, but nothing blocks correct invocation.

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 per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent parameters.

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 ('Lists') and resource ('sites') and scopes it to 'this account'. The resource is naturally distinct from sibling list_folders, though the description never explicitly contrasts with siblings like list_folders or delete_site.

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?

The clause 'so a publish can go to one of them' implies the usage context (fetch site identifiers ahead of a publish), which is helpful. However, there is no explicit when-to-use/when-not guidance and no naming of alternatives, leaving the agent to infer the trigger.

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

Deploy Server

Other Tools