Skip to main content
Glama
Sign In
mcp-cloud-deploy

mcp-cloud-deploy

by hoangtrietdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_deployments

Lists recent Cloudflare Pages deployments for a project, including live URLs and custom domain bindings to verify status and access links.

Instructions

List recent Cloudflare Pages deployments, live URLs, and custom domain bindings. Cloudflare Pages deployments support nested static assets and React/Vite builds.

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

Input Schema

NameRequiredDescriptionDefault
project_nameYesCloudflare Pages project name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It signals a read-like operation by saying 'List' and mentions returned data categories, but does not define 'recent', pagination, ordering limits, authentication requirements, or whether all deployments are returned. These omissions matter for an agent deciding how to invoke and interpret the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and useful, but the second sentence about nested static assets and React/Vite builds is tangential for a listing tool and does not clearly earn its place. The description is short, but not every sentence adds actionable value.

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 simple, single-parameter list operation with no output schema, the description covers the core purpose and returned data categories. However, with no annotations and no mention of recency limits, pagination, or permissions, it is only minimally complete for an agent that needs to know invocation behavior.

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 100%, and the single project_name parameter is already fully documented in the schema with pattern and length constraints. The description does not add meaning beyond the schema for this parameter, so the baseline of 3 applies.

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 description uses a specific verb and resource: 'List recent Cloudflare Pages deployments' and names the data returned, including live URLs and custom domain bindings. It is clearly distinct from deploy_to_cloudflare_pages and attach_custom_domain, though it does not explicitly name those siblings for contrast.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated exclusions or prerequisites. The verb 'List' implies a read-only retrieval operation, but the description does not tell an agent when this is the right choice over deploy or domain-attachment tools.

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