Skip to main content
Glama

List Manual Test Cases

list_manual_test_cases
Read-only

Search and browse manual test cases by project, suite, title, case ID, status, tags, and test properties to quickly find and review the cases you need.

Instructions

Search and browse manual test cases with filters. Use suiteId to scope to a folder, search to match by title or caseId (e.g. "TC-123"), status for active/draft/deprecated, and tags for comma-separated tag filtering. Default limit is 10 — increase it if you need more results.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_manual_test_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoSingle tag or comma-separated tags
timeNoe.g. "last 1 hour", "Yesterday", "last 7 days"
typeNoType. Values come from Project Settings → Test Case Properties. Defaults: Smoke, Regression, Functional, Integration, E2E, API, Unit, Performance, Security, Accessibility, Usability, Compatibility, Acceptance, Exploratory, Other.
layerNoLayer. Values come from Project Settings → Test Case Properties. Defaults: E2E, API, Unit, Not Set.
limitNoDefault 10
searchNoMatch title or caseId
statusNo
suiteIdNo
behaviorNoBehavior. Values come from Project Settings → Test Case Properties. Defaults: Positive, Negative, Destructive, Not Set.
priorityNoPriority. Values come from Project Settings → Test Case Properties. Defaults: Critical, High, Medium, Low, Not Set.
severityNoSeverity. Values come from Project Settings → Test Case Properties. Defaults: Blocker, Critical, Major, Normal, Minor, Trivial, Not Set.
projectIdYesProject ID
automationStatusNoAutomation status. Values come from Project Settings → Test Case Properties. Defaults: Manual, Automated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / automationStatus / description
      Previous value: -"Filter by automation status."New value: +"Automation status. Values come from Project Settings → Test Case Properties. Defaults: Manual, Automated."
    • removedInput schema / properties / automationStatus / enum
      Removed value: -[
      -  "Manual",
      -  "Automated",
      -  "To be automated"
      -]
    • changedInput schema / properties / behavior / description
      Previous value: -"Filter by test behavior type."New value: +"Behavior. Values come from Project Settings → Test Case Properties. Defaults: Positive, Negative, Destructive, Not Set."
    • removedInput schema / properties / behavior / enum
      Removed value: -[
      -  "positive",
      -  "negative",
      -  "destructive",
      -  "Not set"
      -]
    • changedInput schema / properties / layer / description
      Previous value: -"Filter by test layer."New value: +"Layer. Values come from Project Settings → Test Case Properties. Defaults: E2E, API, Unit, Not Set."
    • removedInput schema / properties / layer / enum
      Removed value: -[
      -  "e2e",
      -  "api",
      -  "unit",
      -  "not set"
      -]
    • removedInput schema / properties / limit / default
      Removed value: -10
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return (default: 10, max: 1000)."New value: +"Default 10"
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / priority / description
      Previous value: -"Filter by priority level."New value: +"Priority. Values come from Project Settings → Test Case Properties. Defaults: Critical, High, Medium, Low, Not Set."
    • removedInput schema / properties / priority / enum
      Removed value: -[
      -  "high",
      -  "medium",
      -  "low",
      -  "Not set"
      -]
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID"
    • changedInput schema / properties / search / description
      Previous value: -"Search term to match against title or caseId. Example: 'login' or 'TC-123'."New value: +"Match title or caseId"
    • changedInput schema / properties / severity / description
      Previous value: -"Filter by severity level."New value: +"Severity. Values come from Project Settings → Test Case Properties. Defaults: Blocker, Critical, Major, Normal, Minor, Trivial, Not Set."
    • removedInput schema / properties / severity / enum
      Removed value: -[
      -  "Blocker",
      -  "critical",
      -  "major",
      -  "Normal",
      -  "minor",
      -  "trivial",
      -  "Not set"
      -]
    • removedInput schema / properties / status / description
      Removed value: -"Filter by test case status."
    • removedInput schema / properties / suiteId / description
      Removed value: -"Filter by specific test suite ID. Use list_manual_test_suites to find suite IDs."
    • changedInput schema / properties / tags / description
      Previous value: -"Filter by tags. Can be a single tag or comma-separated tags. Example: 'smoke' or 'smoke,regression,login'."New value: +"Single tag or comma-separated tags"
    • changedInput schema / properties / time / description
      Previous value: -"Filter by time interval."New value: +"e.g. \"last 1 hour\", \"Yesterday\", \"last 7 days\""
    • removedInput schema / properties / time / enum
      Removed value: -[
      -  "last 1 hour",
      -  "Last 5 hours",
      -  "Yesterday",
      -  "last 7 days"
      -]
    • changedInput schema / properties / type / description
      Previous value: -"Filter by test case type."New value: +"Type. Values come from Project Settings → Test Case Properties. Defaults: Smoke, Regression, Functional, Integration, E2E, API, Unit, Performance, Security, Accessibility, Usability, Compatibility, Acceptance, Exploratory, Other."
    • removedInput schema / properties / type / enum
      Removed value: -[
      -  "functional",
      -  "smoke",
      -  "regression",
      -  "security",
      -  "performance",
      -  "e2e",
      -  "Integration",
      -  "API",
      -  "Unit",
      -  "Accessability",
      -  "Compatibility",
      -  "Acceptance",
      -  "Exploratory",
      -  "Usability",
      -  "Other"
      -]
  2. Changed13 schema fields changedv1.0.10
    • changedInput schema / properties / automationStatus / enum
      Previous value: -[
      -  "automated",
      -  "manual",
      -  "not_automated"
      -]New value: +[
      +  "Manual",
      +  "Automated",
      +  "To be automated"
      +]
    • changedInput schema / properties / behavior / enum
      Previous value: -[
      -  "positive",
      -  "negative",
      -  "destructive"
      -]New value: +[
      +  "positive",
      +  "negative",
      +  "destructive",
      +  "Not set"
      +]
    • removedInput schema / properties / isFlaky
      Removed value: -{
      -  "description": "Filter test cases marked as flaky. Set to true to show only flaky tests, false for non-flaky.",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / layer / enum
      Previous value: -[
      -  "e2e",
      -  "api",
      -  "unit"
      -]New value: +[
      +  "e2e",
      +  "api",
      +  "unit",
      +  "not set"
      +]
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return (default: 50, max: 1000)."New value: +"Maximum number of results to return (default: 10, max: 1000)."
    • changedInput schema / properties / priority / enum
      Previous value: -[
      -  "critical",
      -  "high",
      -  "medium",
      -  "low"
      -]New value: +[
      +  "high",
      +  "medium",
      +  "low",
      +  "Not set"
      +]
    • changedInput schema / properties / search / description
      Previous value: -"Search term to match against title, description, or caseId. Example: 'login' or 'TC-123'."New value: +"Search term to match against title or caseId. Example: 'login' or 'TC-123'."
    • changedInput schema / properties / severity / enum
      Previous value: -[
      -  "critical",
      -  "major",
      -  "minor",
      -  "trivial"
      -]New value: +[
      +  "Blocker",
      +  "critical",
      +  "major",
      +  "Normal",
      +  "minor",
      +  "trivial",
      +  "Not set"
      +]
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "actual",
      -  "draft",
      -  "deprecated"
      -]New value: +[
      +  "active",
      +  "draft",
      +  "deprecated"
      +]
    • changedInput schema / properties / tags / description
      Previous value: -"Filter by tags (comma-separated list). Example: 'smoke,regression' or 'critical'."New value: +"Filter by tags. Can be a single tag or comma-separated tags. Example: 'smoke' or 'smoke,regression,login'."
    • addedInput schema / properties / time
      Added value: +{
      +  "description": "Filter by time interval.",
      +  "enum": [
      +    "last 1 hour",
      +    "Last 5 hours",
      +    "Yesterday",
      +    "last 7 days"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "functional",
      -  "smoke",
      -  "regression",
      -  "security",
      -  "performance",
      -  "e2e"
      -]New value: +[
      +  "functional",
      +  "smoke",
      +  "regression",
      +  "security",
      +  "performance",
      +  "e2e",
      +  "Integration",
      +  "API",
      +  "Unit",
      +  "Accessability",
      +  "Compatibility",
      +  "Acceptance",
      +  "Exploratory",
      +  "Usability",
      +  "Other"
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new operational detail in the default limit of 10 and the advice to raise it for more results, but says nothing about result ordering, total counts, or whether more than 1000 can be paged.

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 sentences, front-loaded with purpose and then a compact filter cheat-sheet — no filler. The only redundancy is restating "Default limit is 10", which the schema already documents, before adding the useful 'increase it' advice.

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 13-parameter read-only list tool with no output schema, the description plus the well-annotated schema covers nearly everything an agent needs to construct a call. The remaining gap is what comes back (fields, ordering, total count), which matters slightly more because there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (85%), so the baseline is 3, but the description adds meaning the schema lacks: suiteId as a folder-scoping identifier (the schema gives it no description at all) and status as the active/draft/deprecated filter. The tags note about comma-separated values duplicates the schema, which keeps it out of 5 territory.

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?

The description opens with a specific verb and resource ("Search and browse manual test cases with filters"), which cleanly separates it from the sibling write tools (create_manual_test_case, update_manual_test_case). It does not explicitly distinguish itself from adjacent read tools like list_run_test_cases or list_testcase, so it stops short of a 5.

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?

Guidance is given at the parameter level (use suiteId to scope to a folder, search to match title/caseId) plus an invocation hint about raising the limit. There is no statement of when this tool is the right choice versus list_run_test_cases or get_manual_test_case, and no exclusions, so usage is implied rather than directed.

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