testit-mcp-server

get_project_analytics

Read-only

Retrieve analytics for all test plans in a project, with paging, filtering, and sorting options to inspect project test-plan metrics.

Instructions

Get analytics for all test plans in a project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project_analytics"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page number; alternative to skip. Uses "size" (default 50).
`size`	No	Page size for "page"; alias of take.
`skip`	No	Number of items to skip (offset).
`take`	No	Max number of items to return.
`orderBy`	No	Sort expression, e.g. "createdDate desc".
`projectId`	No
`projectName`	No
`searchField`	No	Field name to search in.
`searchValue`	No	Value to search for in searchField.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations establish a read-only, open-world operation, and the description adds the useful behavioral scope that results span all test plans in the project. It adds nothing further about result granularity, aggregation, empty projects, or other runtime behavior.

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

Conciseness5/5

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

The single sentence is direct, front-loaded, and free of filler. Its brevity leaves informational gaps, but the wording itself is efficient and clearly structured.

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?

For a nine-parameter analytics tool with no required parameters or output schema, one sentence does not provide enough operational context. The schema covers most pagination and search details, but project selection and the nature of the returned analytics remain unclear.

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

Parameters2/5

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

The schema documents the pagination, ordering, and search parameters, but the description adds no parameter meaning. Most importantly, the undocumented projectId and projectName parameters remain ambiguous: it is unclear whether either is required, whether they are alternatives, or how conflicts are handled.

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 gives a clear verb, resource, and scope: analytics covering all test plans within a project. The project-wide wording helps distinguish it conceptually from get_test_plan_analytics, but it does not explicitly differentiate the siblings or explain what analytics includes.

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?

The intended situation is implied: use this for project-wide analytics across test plans. There is no explicit guidance on when to prefer it over get_test_plan_analytics or other statistics and summary tools, nor any prerequisite for identifying the project.

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

Deploy Server