Skip to main content
Glama
Sign In
TestDino MCP

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Automated Tests

list_automated_tests
Read-only

Search a project's automated (Playwright) tests by title or link status to retrieve the fullTitle and pwTestId required for linking to manual cases. Each result shows if already linked.

Instructions

Search the automated (Playwright) test identities recorded for a project — the source of the pwTestId and fullTitle pair that link_automated_test / bulk_link_automated_tests require. ALWAYS take fullTitle from this tool: it is a server-reconstructed join key (" > <describe…> > ") and a hand-built one fails identity validation. Filter with search (title substring), linkStatus ("all" | "linked" | "unlinked") and page with cursor/limit. Each row also reports whether it is already linked to a manual case.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 20, max 100)
cursorNonextCursor from the previous page. Omit for the first page.
searchNoSubstring match on the test title
projectIdYesProject ID
linkStatusNoDefault "all". "unlinked" lists tests no manual case links to yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / limit / description
      Previous value: -"Page size (default 20, max 100)."New value: +"Page size (default 20, max 100)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • 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: -"Substring match on the test title."New value: +"Substring match on the test title"
    • addedInput schema / properties / search / maxLength
      Added value: +500
  2. Addedv2.0.3

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds a critical non-obvious behavior: fullTitle is a server-reconstructed join key that fails identity validation if hand-built. It also notes that each row reports its link state, which the absent output schema would otherwise leave dark.

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?

Front-loaded with purpose and the fullTitle warning before the filter list, and every clause carries information. The parenthetical join-key example is worth its length, though the middle sentence runs long and could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the returned identity pair and the per-row link status, plus paging via cursor. Combined with the downstream-tool linkage, an agent has everything needed to call this correctly.

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%, so all five parameters are already documented, and the description largely restates the filter/paging options ('search (title substring)', 'cursor/limit'). The one added nuance is framing linkStatus as a workflow choice, but that meaning is already present in the schema's enum description, 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 ('Search the automated (Playwright) test identities recorded for a project') and immediately clarifies it as the source of the pwTestId/fullTitle pair, which cleanly separates it from list_manual_test_cases and the other list_* siblings.

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

Usage Guidelines5/5

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

Explicitly names the downstream consumers (link_automated_test / bulk_link_automated_tests) and the hard rule 'ALWAYS take fullTitle from this tool', giving an unambiguous when-to-use condition plus the consequence of not following it. It also enumerates the supported filters, so the agent knows what narrowing is available.

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

Deploy Server

Other Tools