Skip to main content
Glama
trtmn

TestRail MCP Server

by trtmn

run_testrail_command

Execute any TestRail API method to manage test projects, cases, runs, and results, with support for parameters, filters, field selection, and result truncation.

Instructions

Execute a TestRail API method.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesThe API category (e.g. "projects", "cases", "runs").
methodYesThe method name (e.g. "get_projects", "add_case").
paramsNoOptional dict of parameters to pass to the method.
extra_paramsNoOptional dict of additional query parameters that are appended to the API request URL. Use this for filters not directly supported by the method signature, such as custom field filters (e.g. ``{"custom_automation_type": "1"}``). These are merged into the URL query string alongside the method's own parameters.
fieldsNoOptional list of field names to include in each result item. When provided and the response is a list of dicts, each dict is filtered to only contain the specified keys. Useful for reducing response size (e.g. ``fields=["id", "title"]``).
max_resultsNoOptional maximum number of items to return. When provided and the response is a list longer than this value, the list is truncated and the return value becomes a dict with ``results`` (the truncated list), ``truncated`` (True), ``total_count`` (original length), and a human-readable ``message``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral traits, but it only states 'Execute a TestRail API method.' It does not disclose read/write nature, authentication needs, error behaviors, or side effects like pagination truncation (implied by 'max_results' parameter).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but at the expense of informativeness. It does not earn its place because it provides minimal value; more context is needed for a tool with six parameters.

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

Completeness2/5

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

Given the tool's complexity (6 parameters, output schema), the description is incomplete. It does not explain the return structure (though output schema exists), side effects, or how 'execute' relates to the TestRail API. The sibling tools offer context but the description should be self-contained.

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 baseline is 3. The description adds no parameter information beyond the schema; it simply repeats the verb. The schema already documents each parameter adequately.

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 'Execute a TestRail API method' clearly states the tool's action (execute) and resource (TestRail API method). It distinguishes from siblings like 'describe_testrail_method' (which describes rather than executes) and 'search_test_cases' (which searches), though it lacks specificity about what methods are supported.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives. The description does not mention prerequisites, when not to use it, or suggest siblings like 'describe_testrail_method' for method details. An agent must infer usage from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trtmn/tram-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server