Skip to main content
Glama

list_releases

Retrieve a service's release history, including version numbers, build status, source, and dates, by service ID to track deployments and diagnose version issues.

Instructions

Servisin sürüm geçmişi (sürüm no, derleme durumu, kaynak: panel/api, tarih).

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": {
      "serviceId": "<serviceId>"
    },
    "name": "list_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it says nothing about read-only safety, required permissions, ordering, pagination, or result limits. The only behavioral value it adds is naming the returned fields, which is modest for a read tool with zero annotation coverage.

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?

One compact sentence with no filler, and the field enumeration is placed immediately after the resource name so the reader gets scope up front. It is efficient, though it is a noun phrase rather than a well-formed statement of action.

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 one-parameter read tool with no output schema, listing the returned fields is a useful substitute for return-value documentation. What is missing is anything about ordering, result volume, or how the history relates to sibling tools, which keeps it at minimum-viable rather than complete.

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 serviceId parameter is documented in the schema with a pointer to list_services/create_service. The description adds no meaning beyond that, so the baseline 3 for high coverage applies.

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

Purpose3/5

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

The phrase 'Servisin sürüm geçmişi' identifies the resource (a service's release history) and the parenthetical enumerates the fields it surfaces (version number, build status, source panel/api, date). However, the verb is only implied and nothing distinguishes this from sibling read tools such as get_build or get_service_logs, so an agent must infer that this is a list-style history endpoint rather than a build detail lookup.

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 when-to-use guidance, no exclusions, and no mention of alternatives like get_build for a single build or get_service_logs for runtime output. The agent is left to guess that this is the appropriate call when it wants historical release records for a service.

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