Skip to main content
Glama

list_labels

List all available labels (tags) created by the authenticated user across scopes: PROJECT, COLLECTION, MOCK, RULE. Returns an array of label objects with id, name, color, and type. Use this to discover existing tag names before filtering with list_mocks or tagging mocks in create_mock/update_mock.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional label scope filter. Valid values: 'PROJECT', 'COLLECTION', 'MOCK', 'RULE'. Omit to return labels across all scopes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"Filter by label scope. Valid: 'PROJECT', 'COLLECTION', 'MOCK', 'RULE'. Omit for all."New value: +"Optional label scope filter. Valid values: 'PROJECT', 'COLLECTION', 'MOCK', 'RULE'. Omit to return labels across all scopes."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It usefully discloses that results are scoped to the authenticated user and describes the return element shape (id, name, color, type), but says nothing about ordering, result size limits, or authorization requirements. For a simple read tool this is adequate but not thorough.

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?

Three tight sentences: purpose and scope first, then return shape, then the motivating use case. No filler and no repetition of the tool name as content.

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 one-optional-parameter read tool with no output schema and no annotations, the description covers purpose, scope, return fields, and intended workflow. Only minor behavioral details such as ordering or result limits are absent, which is a small gap.

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 parameter's enum is fully documented in the schema, including the 'omit to return all scopes' behavior. The description restates the scope values but adds no filtering semantics beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource ('List all available labels (tags)') and narrows the scope explicitly ('created by the authenticated user across scopes: PROJECT, COLLECTION, MOCK, RULE'). The enumerated scopes and the returned fields distinguish it cleanly from sibling tools like list_mocks or list_projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a concrete usage scenario: discover existing tag names before filtering with list_mocks or tagging mocks in create_mock/update_mock, which routes the agent to the correct downstream tools. It lacks an explicit 'when not to use' or a stated alternative when the agent already knows the label names, but the context is clear.

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