Skip to main content
Glama

Testiny Test Management

List Testiny test cases

listTestCases
Read-onlyIdempotent

Retrieve a list of Testiny test cases with an optional keyword filter and an optional folder filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoFormat for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.
keywordNoAn optional keyword to search in test case titles. A keyword of digits only, optionally prefixed 'TC-' or '#', looks up that id instead of searching titles.
projectYesProject ID (number or string), project key or part of the project name
folderKeywordNoAn optional keyword to search in test case folder titles. A keyword of digits only, optionally prefixed 'TCF-' or '#', looks up that id instead of searching titles.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
testCasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / folderKeyword / description
      Previous value: -"An optional keyword to search in test case folder titles. When looking for an id, search in the following format: TCF-1234"New value: +"An optional keyword to search in test case folder titles. A keyword of digits only, optionally prefixed 'TCF-' or '#', looks up that id instead of searching titles."
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.",
      +  "enum": [
      +    "markdown",
      +    "xml"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / keyword / description
      Previous value: -"An optional keyword to search in test case titles. When looking for an id, search in the following format: TC-1234"New value: +"An optional keyword to search in test case titles. A keyword of digits only, optionally prefixed 'TC-' or '#', looks up that id instead of searching titles."
    • addedOutput schema / properties / testCases / items / properties / _etag
      Added value: +{
      +  "description": "Conflict tag of the entity - pass it to an edit tool's '_etag' to have that edit rejected if somebody changed the entity in the meantime. Empty for an entity that carries no tag yet.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / testCases / items / properties / bddScenarios
      Added value: +{
      +  "description": "Gherkin source of a BDD test case as it was written, with LF line ends (a carriage return is dropped on write). Plain text in every format, so it is unaffected by 'format'. Omitted unless the template is BDD.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / testCases / items / properties / expectedResults
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / testCases / items / properties / steps / description
      Added value: +"The STEPS-template content as step + expectedResult pairs, under the same names 'createTestCase' and 'editTestCase' take, each cell in the requested format. Omitted for TEXT and BDD test cases, and for cases without content."
    • addedOutput schema / properties / testCases / items / properties / steps / items
      Added value: +{
      +  "properties": {
      +    "expectedResult": {
      +      "description": "The expected-result cell, in the requested format",
      +      "type": "string"
      +    },
      +    "index": {
      +      "description": "0-based step index",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "step": {
      +      "description": "The step action cell, in the requested format",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "index",
      +    "step",
      +    "expectedResult"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / testCases / items / properties / steps / type
      Previous value: -"string"New value: +"array"
    • changedOutput schema / properties / testCases / items / properties / template / description
      Previous value: -"The template type of the test case, e.g. STEPS, TEXT (converted to STEPS on edit), BDD (editing currently not supported)"New value: +"The content template the test case displays: STEPS (interleaved action/expected-result steps), TEXT (free-form documents) or BDD (gherkin scenarios)"
    • addedOutput schema / properties / testCases / items / properties / template / enum
      Added value: +[
      +  "TEXT",
      +  "STEPS",
      +  "BDD"
      +]
    • addedOutput schema / properties / testCases / items / properties / text
      Added value: +{
      +  "description": "The TEXT-template content, under the same names 'createTestCase' and 'editTestCase' take. Omitted unless the template is TEXT.",
      +  "properties": {
      +    "expectedResultText": {
      +      "description": "The expected-result document, in the requested format",
      +      "type": "string"
      +    },
      +    "stepsText": {
      +      "description": "The steps/actions document, in the requested format",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "stepsText",
      +    "expectedResultText"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / properties / testCases / items / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "folder",
      -  "precondition",
      -  "template"
      -]New value: +[
      +  "id",
      +  "title",
      +  "folder",
      +  "template",
      +  "precondition",
      +  "_etag"
      +]
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources