Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

QTM4J: Get Projects

qtm4j_get_projects
Read-onlyIdempotent

Retrieve and filter QTM4J projects by ID, search text, QMetry status, or pagination to get project details like keys, names, and integration status for use in other operations.

Instructions

Get all projects from QTM4J with optional filtering

Toolset: Projects

Parameters:

  • projectId (number): Filter by specific project ID

  • search (string): Search text for project key or project name

  • qmetryEnabled (boolean): Filter by QMetry enabled status

  • startAt (number): Zero-indexed starting position for pagination (default: 0)

  • maxResults (number): Maximum number of results per page (1-100) (default: 100)

Output Description: JSON object containing paginated list of projects with IDs, keys, names, and QMetry status, along with pagination metadata

Use Cases: 1. Discover all projects available in QTM4J instance 2. Get project IDs and keys for reference in other operations 3. Find specific projects by ID 4. Search projects by text in project key or name 5. Filter projects by QMetry integration status 6. List projects with pagination for large QTM4J instances 7. Retrieve complete project details (ID, key, name, avatarUrl, projectTypeKey, qmetryEnabled, favorite) 8. Validate project access and permissions 9. Browse available projects before performing other operations

Examples:

  1. Get all projects (default pagination - first 100)

{}

Expected Output: List of all projects with IDs, keys, and names (first 100 projects)

  1. Get the first 10 projects

{
  "maxResults": 10
}

Expected Output: List of first 10 projects with their details

  1. Get a specific project by ID

{
  "projectId": 10000
}

Expected Output: Single project with ID 10000 including key, name, and QMetry status

  1. Search projects by text in project key or name

{
  "search": "SCRUM"
}

Expected Output: Projects matching 'SCRUM' search text in their project keys or names

  1. Get only QMetry-enabled projects

{
  "qmetryEnabled": true
}

Expected Output: List of projects that have QMetry integration enabled

  1. Get projects with custom pagination (page 2)

{
  "startAt": 50,
  "maxResults": 50
}

Expected Output: Second page of projects (items 51-100) with their details

  1. Search QMetry-enabled projects by text

{
  "search": "TEST",
  "qmetryEnabled": true
}

Expected Output: QMetry-enabled projects containing 'TEST' in their project keys

Hints: 1. Project IDs are numeric (e.g., 10000), project keys are strings (e.g., 'SCRUM') 2. Use 'projectId' parameter to filter by a specific project ID 3. Use 'search' parameter to search by text in project key or project name 4. Use 'qmetryEnabled' parameter to filter projects by QMetry integration status 5. Response contains complete project details: id, key, name, favorite, avatarUrl, projectTypeKey, qmetryEnabled 6. Pagination: startAt is zero-indexed, maxResults max is 100, default is 100 7. Default (no parameters) returns first 100 projects 8. Use 'isLast' in response to check if more pages are available 9. To get next page: increment startAt by maxResults (0 → 100 → 200) 10. Use 'total' in response for total count of matching projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoSearch text for project key or project name
startAtNoZero-indexed starting position for pagination
projectIdNoFilter by specific project ID
maxResultsNoMaximum number of results per page (1-100)
qmetryEnabledNoFilter by QMetry enabled status

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesList of projects
totalYesTotal number of projects
Install Server

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description is fully consistent with these. The description adds valuable behavioral context beyond annotations: pagination defaults, use of isLast and total, parameter interactions, and the complete project fields returned. There is no contradiction.

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?

The description is long but well-structured with clear sections: summary, parameters, output, use cases, examples, and hints. It is front-loaded with the core purpose. Some repetition exists between use cases, examples, and hints, but every section contributes actionable guidance.

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?

The description is fully complete for a read-only list tool: all five optional parameters are explained, pagination behavior is specified, examples cover typical and combined usages, and expected output contents are described. With output schema available and annotations covering safety, nothing an agent needs to call this 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 description coverage is 100%, so the baseline is 3. The description adds meaningful value through examples showing how parameters combine, clarification that startAt is zero-indexed, maxResults cap/default, and hints about project key versus ID. This goes beyond the raw schema definitions without being redundant.

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 clearly states the tool gets all projects from QTM4J with optional filtering, which identifies the specific resource and operation. It does not explicitly differentiate from similar sibling tools like qmetry_fetch_qmetry_list_projects or zephyr_get_projects, but the QTM4J branding and detailed scope make the purpose clear.

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

Usage Guidelines4/5

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

The description provides extensive use cases, examples, and hints explaining when to use this tool, such as discovering projects, finding project IDs, filtering by QMetry status, and paginating results. It does not explicitly state when to prefer alternatives, but the context is clear and complete for this tool's own usage.

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

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/SmartBear/smartbear-mcp'

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