Skip to main content
Glama

deployment_get_deployments

Read-onlyIdempotent

Fetch a paginated list of deployments with filtering by status, tags, projects, and other criteria to find specific deployments.

Instructions

Fetch all deployments. Returns a paginated list of deployments. GET /deployment/api/deployments

Input Schema

NameRequiredDescriptionDefault
idsNoA comma-separated list. Only deployments with these IDs will be included in the results.
topNoNumber of records you want
nameNoResults must have exactly this name.
pageNoZero-based page index (0..N)
sizeNoThe size of the page to be returned
skipNoNumber of records you want to skip
sortNoSorting criteria in the format: property,(asc|desc). Default sort order is ascending. Multiple sort criteria are supported.
tagsNoA comma-separated list. Results must be associated with one of these tags
expandNoThe expanded details of the requested comma separated objects. 'resources' option returns resources with all properties. Ex. blueprint, project
filterNoA subset of records that satisfy the given predicate expression
searchNoGiven string should either be part of a searchable field in a deployment or one of deployment's resources.
statusNoA comma-separated list. Results must be associated with one of these statuses.
deletedNoRetrieves only soft-deleted deployments that have not yet been completely deleted.
orderbyNoSorting criteria in the format: property (asc|desc). Default sort order is ascending. Multiple sort criteria are supported.
ownedByNoA comma-separated list. Results must be associated with one of these owners
projectsNoA comma-separated list. Results must be associated with one of these project IDs.
createdAtNoComma-separated start and end dates where start date or end date is optional (e.g. [2020-12-01T08:00:00.000Z,2020-12-11T23:59:00.000Z], [2020-11-03T08:00:00.000Z,], [,2020-11-08T08:00:00.000Z])
expiresAtNoComma-separated start and end dates where start date or end date is optional (e.g. [2020-12-01T08:00:00.000Z,2020-12-11T23:59:00.000Z], [2020-11-03T08:00:00.000Z,], [,2020-11-08T08:00:00.000Z])
cloudTypesNoA comma-separated list. Results must be associated with one of these endpoint Types
requestedByNoA comma-separated list. Results must be associated with one of these requesters
cloudAccountsNoA comma-separated list. Results must be associated with one of these cloud accounts.
expandProjectNoThe 'project' field of each resulting deployment will be retrieved.
lastUpdatedAtNoComma-separated start and end dates where start date or end date is optional (e.g. [2020-12-01T08:00:00.000Z,2020-12-11T23:59:00.000Z], [2020-11-03T08:00:00.000Z,], [,2020-11-08T08:00:00.000Z])
resourceTypesNoA comma-separated list. Results must be associated with one of these resourceType Names.
expandResourcesNoThe 'resources' field of each resulting deployment will be retrieved.
expandLastRequestNoExpands deployment last request.
lastRequestStatusNoA comma-separated list of last request statuses. Allowed values are: ABORTED, APPROVAL_PENDING, APPROVAL_REJECTED, FAILED, INPROGRESS, PENDING and SUCCESSFUL. Results must be associated with one of these last request statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds only that results are paginated and repeats the GET endpoint, without explaining filtering, default sorting, soft-deleted behavior, or what 'all' includes.

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?

The description is short and front-loaded with the core purpose. The final 'GET /deployment/api/deployments' sentence largely repeats the annotation title and does not add much, but the overall text remains efficient.

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?

The description is minimally adequate given the rich schema and annotations, but for a 27-parameter listing tool with no output schema it does not explain sibling scope differences or the shape of the paginated response. It leaves the agent to rely almost entirely on structured fields.

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% across 27 parameters, so the schema carries the full burden of parameter meaning. The description adds no parameter-specific guidance, which meets the baseline for a fully documented schema.

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 and resource ('Fetch all deployments') and adds that the result is a paginated list. However, it does not explicitly distinguish this from sibling tools such as deployment_get_deployments_for_project, so the agent must infer the scope difference from the name.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of deployment_get_deployments_for_project or when project-scoped listing would be more appropriate.

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