Skip to main content
Glama

Списки промокодов

get_promocode_list
Read-onlyIdempotent

Возвращает списки промокодов воркспейса. workspace_id берётся из get_workspace_list.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_promocode_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoЧем сортировать: updated_at — по последнему изменению, name — по названию, id — по порядку создания (по умолчанию).
limitNoКоличество записей (по умолчанию 20).
orderNoНаправление сортировки: asc — по возрастанию, desc — по убыванию (по умолчанию).
offsetNoСмещение (по умолчанию 0).
searchNoИскать список по названию, частичное совпадение.
workspace_idYesID рабочего пространства.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the workspace-scoping dependency, but says nothing about result size, pagination defaults, or what a returned 'list' contains, which matters for a collection endpoint with no output schema.

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?

Two short sentences with no filler, and the core action is front-loaded. Slightly more context on scope or return shape could be added without bloat, but nothing present is wasted.

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 six-parameter listing tool with no output schema, the description covers the identity, the scope and where workspace_id comes from. It is missing any indication of what a promocode list is versus a code or a quiz list, which an agent needs to choose correctly among the many siblings.

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 coverage is 100%, with descriptive text for sort, order, limit, offset, search and workspace_id, so the schema carries the parameter burden. The description only adds the provenance of workspace_id, which is modest extra value above the 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 ('Возвращает списки промокодов воркспейса'), which is clear enough to separate a listing operation from mutation siblings like create_promocode_group. It does not, however, say how this differs from the closely named get_promocode_codes or get_promocode_list_quizzes, so the distinction is left to 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives one useful operational hint: workspace_id comes from get_workspace_list, which tells the agent the prerequisite call. It stops short of saying when to use this listing versus the other promocode-related siblings, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources