Skip to main content
Glama
Sign In
travis-mcp

travis-mcp

by vlhommeau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List builds

list_builds
Read-only

View a repository's recent Travis CI builds, filterable by branch, event type, state, or pull request number to identify build outcomes.

Instructions

Most recent builds of a repository, newest first. Filter by branch, event type, state or pull request number.

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": "list_builds"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository slug "owner/name"
limitNo
stateNo
branchNoBranch name (for PR builds: the target branch)
event_typeNo
pull_requestNoOnly builds of this pull request number (implies event_type=pull_request)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful ordering behavior ('newest first') and filter dimensions, but it does not disclose the return shape, pagination behavior, or how filters combine.

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?

A single, tight sentence that front-loads the core behavior ('Most recent builds of a repository, newest first') before listing filters. There is no filler or redundant restatement of the title.

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

Completeness3/5

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

For a six-parameter list tool with no output schema, the description covers the main intent and filter options but omits the result format and pagination details. It is adequate for basic invocation, but an agent would still rely on inference about what the returned build objects look like.

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?

The description adds meaning by naming branch, event type, state, and pull request number as filter dimensions, which is helpful because state and event_type have no textual schema descriptions. It does not mention limit explicitly, and repo semantics are already covered by the schema, so the description only partially compensates for the 50% schema coverage.

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 action: list the most recent builds of a repository, sorted newest first, and names the supported filter dimensions. It does not explicitly distinguish itself from siblings such as get_build, though the plural 'builds' and 'most recent' imply a list operation.

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 description implies when to use the tool: when you need recent repository builds, possibly filtered by branch, event type, state, or pull request number. However, it gives no explicit guidance about when to prefer get_build, get_build_jobs, or get_job_log instead.

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