webprompter.ai — Static Sites & Custom Domains for Coding Agents

list_deployments

List deployments for a site, optionally filtered to one environment. Excludes pruned (deleted) versions. Only the current deployment plus 5 previous versions per environment are retained.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_deployments"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	Yes
`environment`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden, and it usefully discloses that pruned versions are excluded and that only the current deployment plus five previous versions per environment are retained. It does not mention auth requirements, ordering, or pagination, but the retention rule is a meaningful behavior beyond the schema.

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?

The description is front-loaded with the core purpose and uses only three short sentences. The retention limit sentence adds useful scope without wasting words.

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 simple two-parameter list tool with no annotations and no output schema, the description covers the key filter and the limited retention window. It leaves minor gaps around ordering and authentication, but those are not central to calling this tool correctly.

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 description coverage is 0%, so the description must supply parameter meaning. It identifies that the site is the primary target and that environment is an optional filter, but it does not document the expected site_id format or further clarify the staging/prod enum beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: list deployments for a site. It also names the optional environment scope, so an agent can immediately tell this is a deployment-listing tool rather than a site-listing or deployment-mutating tool.

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 description implies when to use the environment filter, but it gives no explicit when-to-use guidance versus alternatives such as downloading a deployment or retrieving deployment rules. The scope is understandable, but routing depends on the agent inferring from the verb and sibling names.

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

All webprompter.ai — Static Sites & Custom Domains for Coding Agents tools Inspect

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

Need Help?