Skip to main content
Glama
Sign In
TestDino MCP

TestDino MCP

by testdino-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Link Automated Test

link_automated_test

Link one Playwright automated test to one manual test case so its automation results appear on that case. Requires write permission, automation_linking, and valid IDs from list_automated_tests.

Instructions

Link one automated (Playwright) test to one manual test case so automation results surface on the case. Requires write permission and the automation_linking plan feature (403 otherwise). Get pwTestId + fullTitle from list_automated_tests (or list_testcase, whose pw_test_id matches pwTestId — but fullTitle must still come from list_automated_tests). Rejects with 400 when the identity is unknown to this project, the pwTestId is already linked to the case, or the case already has 50 links. Linking sets the case automationStatus to Automated. For many cases in one call use bulk_link_automated_tests.

Input Schema

NameRequiredDescriptionDefault
caseIdYesManual case: internal _id or "TC-123" style ID
pwTestIdYesStable Playwright test id (pw_test_id)
fullTitleYesServer join key from list_automated_tests — never hand-built
projectIdYesProject ID
displayTitleNoOptional label shown on the case; defaults to the test title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 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 / caseId / description
      Previous value: -"Manual test case ID (Required). Internal _id or 'TC-123' style ID."New value: +"Manual case: internal _id or \"TC-123\" style ID"
    • changedInput schema / properties / displayTitle / description
      Previous value: -"Optional label shown on the case; defaults to the test title."New value: +"Optional label shown on the case; defaults to the test title"
    • addedInput schema / properties / displayTitle / maxLength
      Added value: +500
    • addedInput schema / properties / displayTitle / minLength
      Added value: +1
    • changedInput schema / properties / fullTitle / description
      Previous value: -"Server join key from list_automated_tests (Required) — never hand-built."New value: +"Server join key from list_automated_tests — never hand-built"
    • addedInput schema / properties / fullTitle / maxLength
      Added value: +2000
    • addedInput schema / properties / fullTitle / minLength
      Added value: +1
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (Required). The TestDino project identifier."New value: +"Project ID"
    • changedInput schema / properties / pwTestId / description
      Previous value: -"Stable Playwright test id (pw_test_id) (Required)."New value: +"Stable Playwright test id (pw_test_id)"
    • addedInput schema / properties / pwTestId / maxLength
      Added value: +200
    • addedInput schema / properties / pwTestId / minLength
      Added value: +1
  2. Addedv2.0.3

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries real weight here: it discloses the 403 permission/plan gate, the three 400 rejection cases (unknown identity, duplicate link, 50-link cap), and the side effect that the case automationStatus flips to Automated. That is exactly the behavioral context annotations cannot express.

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?

Purpose is front-loaded in the first clause, and the dense paragraph packs prerequisites, param sourcing, error cases, side effects, and the sibling alternative without filler. It is slightly run-on, but essentially every sentence earns its place.

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?

For a 5-param mutation tool with no output schema, the description covers auth/plan requirements, error behavior, side effects, parameter provenance, and the bulk alternative — nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3; the description adds sourcing semantics the schema does not — that pwTestId and fullTitle must originate from list_automated_tests and that fullTitle is a server join key that is 'never hand-built'. It doesn't elaborate on displayTitle beyond the schema, keeping it at 4 rather than 5.

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+resource ('Link one automated (Playwright) test to one manual test case') and even names the downstream effect ('automation results surface on the case'). An agent can distinguish it immediately from sibling tools like bulk_link_automated_tests and unlink_automated_test without opening any schema.

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 routes the agent: use bulk_link_automated_tests for many cases in one call, and pull pwTestId + fullTitle from list_automated_tests (noting the list_testcase/pw_test_id caveat). Prerequisites (write permission, automation_linking plan feature) and failure conditions are stated up front.

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